LiveLive coverage · Rust server
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
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 24 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Embedded chart
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The current map
Tuesday 27 October 2026, 16:21 UTC
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.
Training Server's wipe history is too thin on record to show a rhythm. Thursday 5 November at 19:00 UTC is the next monthly force wipe, and no Rust server is spared it. 40 hours have passed since this world was generated.
These are the Rust Live Stats lists Training Server fits: Modded Rust servers live now. Under the filters Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days it appears on the server list.
These are the tags Training Server makes public: gmrust (Game mode): Standard survival, in the Rust style; mp20 (Max players): Slots: 20; ts8 (Group limit): 8 per team at most, the game's default setting; v2635 (Protocol): You need protocol 2635 on your game to get in; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the network layer — the game's standard one; $r? (Region code): No region code is set here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings changes put this under Modded. Also in the tags: players on now, the queue, and when the world was made. You will find them at the top of this page.
Training Server is carrying 0 players at the moment, with 20 slots in total. Across the past week the average was 0 players.
Ranked by seven-day player hours, Training Server is #15,338, placing it in the top 69% of ranked servers.
Nothing in the name of Training Server states a gather rate. No custom limit is set, so groups hold the default 8 players. survival is the mode, with the standard game: gather, build, raid. Raiding and player combat are both permitted. Modded is its browser category, where plugins or settings change the game. Plugins run here: Oxide. Anti-cheat: VAC from Valve is enabled.
Size 3,000, seed 50000: that is the procedural map the game generates for Training Server. Same size, same seed, same map: RustMaps has it, reachable from this page.
There is no region from Training Server. Where the machine stands is not checked by Rust Live Stats; only the location a server states is shown. You can reach it at 203.16.163.202:28015.
The average server fps was 173 over the last 48 hours; the lowest was 82. Entity count reached 49,072: buildings, deployables and the rest of the world. Up to 3,588 MB of memory was used. A climbing entity count and low fps are felt as lag by players.
The setup on Training Server is Rust network protocol 2635 and build 168909 with Linux. Joining requires the same protocol on your game; Steam takes care of updating it.
Training Server is up and running at this moment. Based on the uptime it reports, the last restart was about 38 hours ago. It was online for 31 of 168 hours in the last 7 full days, or 18% of the time. On 24 September 2026, Rust Live Stats saw it for the first time.
Enter client.connect 203.16.163.202:28015 in the console (F1 in Rust). Another way is Launch Rust and join on this page: it opens Rust through Steam and connects you.