RUST METRICSFlight deck · live data
Data live Servers11,801 Players73,164 Populated3,682 Fresh wipes 3 h113 Scan5 min
‹ All servers121.87.100.165:28015
Offline Full Queue Fresh wipe Wipe due No query

gameovers

Offline 121.87.100.165:28015 checked 36d ago

moddedoxide
COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 1 /10

Players now

10% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#14,430top 63%
Last wipe36d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players
No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance
This server has not answered a direct query in the last 48 hours.

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k22 Sep23 Sep25 Sep26 Sep28 Sep29 Sep

Top 63% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

How often does gameovers wipe, and when?

To tell the rhythm of gameovers, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 36 days 4 hours ago the current world was made.

Tags

How should you read the tags on gameovers?

These are the tags gameovers publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): The server runs game build 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does gameovers appear in Rust Metrics lists and filters?

These Rust Metrics lists carry gameovers: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Player count

Where does gameovers sit in the rankings?

Player hours over seven days put gameovers at #14,430, in the top 63% of all ranked servers.

What player count does gameovers carry?

gameovers is not responding; status offline, last seen 36 days 3 hours ago.

Server

What location is gameovers hosted in?

No region comes from gameovers. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 121.87.100.165:28015.

What Rust version is gameovers on?

Rust network protocol 2633 and build 165217 on Linux is the build gameovers runs. Check: protocol. To join, your game must match; Steam handles the update.

Is gameovers up, and how often does it stay up?

gameovers reports offline. The last reading came 36 days 3 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 22 September 2026.

Settings and map

What rules does gameovers enforce, and what are its settings?

No gather rate appears in the name: gameovers. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; gather, build and raid, as the game normally runs. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.

Which map is live on gameovers?

Check: map. Procedural, generated by the game, on gameovers.

How to join

How do you connect to gameovers?

To join: start Rust, press F1 and type client.connect 121.87.100.165:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2633,gmrust,cs165217,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players The server holds 10 slots.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Match the game version: protocol 2633 is required.
cs165217
Build The server runs game build 165217.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Check: category. Modded, because plugins or settings alter the game.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.