RUST METRICSFlight deck · live data
Data live Servers11,789 Players78,653 Populated3,571 Fresh wipes 3 h243 Scan5 min
‹ All servers85.190.162.229:10600
Online Full Queue Fresh wipe Wipe due No query

24.05.

Online 85.190.162.229:10600 checked 11m ago

moddedoxide
COM 1 · connect

Server instruments

last reading Thu 21:00 UTC
0 12 25 38 50 PAX 0 /50

Players now

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

Server fps

48 h low 10 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 65,445 ×1000

Entities

48 h range 63,168–67,751 · memory 1,945 MB
1239 ET SINCE RESTART 15:20

Uptime

15 h 20 min since its last restart, at the last reading
7-day average0peak –
Rank#15,276top 69%
Last wipe26d agono schedule published
Next wipe–no wipe seen yet
Memory1,945MBat the last reading
REC 1

Players

AveragePeak
0123423:0008:0017:0003:0012:0021:00

Hourly average and peak, UTC.

REC 2

Server performance

02.557.51023:0008:0017:0003:0012:0021:00

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, measured since 3 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k3 Oct8 Oct13 Oct19 Oct24 Oct29 Oct

Top 69% 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

When does 24.05. wipe?

Its rhythm cannot be told from the wipes of 24.05. on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 26 days 11 hours ago.

Tag meanings

How should you read the tags on 24.05.?

Check: tags. The game's server browser reads gmvanilla (Game mode): Survival on vanilla settings; mp50 (Max players): Slots: 50; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Game build reading: 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game from 24.05.. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show 24.05.?

On Rust Metrics, 24.05. sits in these lists: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Population

What position does 24.05. hold among Rust servers?

Ranking for 24.05.: #15,276 on seven-day player hours, top 69% of all ranked servers.

What is the population on 24.05.?

Current headcount on 24.05.: 0 players, 50 slots available. Seven-day reading: 0 players on average.

Operator and location

Where does 24.05. sit?

No region tag on 24.05.. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 85.190.162.229:10600.

What Rust version is 24.05. on?

Reading: 24.05., Rust network protocol 2635 and build 168909, Windows. Check: protocol. To join, your game must match; Steam handles the update.

What is the performance reading for 24.05.?

Check: fps. Average 10 server fps over the last 48 hours, low of 10. Within range. Peak entity count: 67,751. Buildings, deployables and all else included. Check: memory. Peak use was 2,191 MB. What players call lag comes from low fps and an entity count on the rise.

Is 24.05. up, and how often does it stay up?

24.05. reports online. Status: normal. Check: restart. The uptime it reports puts the last restart about 15 hours ago. Uptime for the last 7 full days: 167 of 168 hours, or 99%. Check: first contact. Rust Metrics logged it on 3 October 2026.

Map and rules

How is 24.05. configured, and what rules are in force?

No gather rate appears in the name: 24.05.. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. VAC is on. That is Valve's anti-cheat.

What map is 24.05. on?

From seed 6738, the game generates the procedural map on 24.05.. Its size is 3,500. The map repeats when size and seed match. Open it on RustMaps from this page.

Connection

How do you connect to 24.05.?

Check: join. Open Rust, press F1, then enter client.connect 85.190.162.229:10600. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,^o^z

Game

gmvanilla
Game mode Survival on vanilla settings.
mp50
Max players Slots: 50.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Game build reading: 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^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.