gameovers
Offline 121.87.100.165:28015 checked 36d ago
Vital stats
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
48 hours: hourly readings. 30 to 90 days: one point a day, with the day's average and lowest fps, most entities and most memory. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 63% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
Peak: the most players in the first 48 hours. Crowd: whether every day of the wipe kept at least half that peak, or the day it fell below. A new world less than six hours after a wipe is a restart, not a wipe of its own.
Similar servers
The same kind of game, then region, group limit, rate and wipes.
Quick answers
From the figures on this page.
Tags
Which Rust Pop Watch lists and filters include gameovers?
These are the Rust Pop Watch lists that include gameovers: Modded Rust servers, live. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
What do the server tags on gameovers mean?
These are the tags gameovers publishes for the browser: gmrust (Game mode): This one runs standard Rust survival, as it comes; mp10 (Max players): Slots: 10; ts8 (Group limit): This uses the default limit of 8 players per team; v2633 (Protocol): To join, your game must be on the same protocol version: 2633; cs165217 (Build): The game build is 165217; ptrak (Networking): RakNet is the network layer, the game's standard one; $r? (Region code): No region code has been set; ^o (Oxide): Oxide (uMod), a plugin framework, is what it runs; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. Current players, queue and world age are in the tags too, displayed at the top of this page.
Population
How does gameovers rank against other Rust servers?
A seven-day player-hours placing of #14,430 puts gameovers in the top 63% of all ranked servers.
How many players are on gameovers right now?
The last sighting of gameovers was 36 days 1 hours ago, and it is offline now.
Server details
Is gameovers online, and how reliable is it?
Down at the moment: gameovers was last seen 36 days 1 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours in total. The first time Rust Pop Watch saw it was 22 September 2026.
Where is gameovers located?
There is no region from gameovers. Rust Pop Watch does not look up where the machine stands; it shows where a server says it is. Connect at 121.87.100.165:28015.
Which Rust version is gameovers on?
Rust network protocol 2633 and build 165217 is the version gameovers runs on Linux. Steam updates your game so it matches the protocol needed to join.
Wipe days
What is the wipe schedule on gameovers?
gameovers's rhythm stays hidden while so few of its wipes are on record. A force wipe comes round every month for all Rust servers, with the next on Thursday 5 November at 19:00 UTC. The world it is running now dates from 36 days 1 hours.
Rules and settings
Which map does gameovers run?
A procedural map is what gameovers runs, generated by the game.
What are the rules and settings on gameovers?
No gather rate appears in the name of gameovers. Groups go up to 8 players, which is the default. the usual game of gathering, building and raiding: that is the survival mode. Players can raid and fight one another. The server browser files it under Modded, where plugins or settings change the game. Oxide plugins power it. The VAC anti-cheat from Valve is on.
Join up
How do I join gameovers?
The console method: start Rust, press F1, and type client.connect 121.87.100.165:28015. Launch Rust on this page is another way, opening Rust via Steam and connecting.