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 26 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Embedded chart
Top 68% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
This server has not put up a new map since the desk started watching it.
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.
The record holds too few of typical test's wipes to reveal its rhythm. Every server in Rust, this one among them, wipes at the monthly force wipe; Thursday 5 November at 19:00 UTC is the next. The world you are playing on was built 2 days 2 hours.
The Rust Live Stats lists that include typical test are Modded Rust servers live now. You will find it on the server list under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
The server browser reads gmrust (Game mode): Survival here follows standard Rust; mp100 (Max players): The slot count is 100; ts8 (Group limit): Teams stop at 8, the default the game ships with; v2635 (Protocol): The server runs protocol 2635, so match that version to join; cs168909 (Build): Build: 168909; ptrak (Networking): The network layer is RakNet, the standard the game uses; $r? (Region code): The server sets no region code; ^o (Oxide): It runs the plugin framework Oxide (uMod); ^z (Modded): Modded: plugins or changed settings alter the game, which typical test publishes. The current player count, the queue and the world's creation time also sit in the tags, shown at the top of this page.
Live now: 0 players on typical test, out of 100 slots. The seven-day average is 0 players, with a peak of 1. The busiest hour in the past 48 was 05:00 UTC, averaging 0 players.
Ranked by seven-day player hours, typical test is #15,082, placing it in the top 68% of ranked servers.
No gather rate appears in the name typical test. Eight players per group, which is the game's default. survival applies here, the standard game: gather, build, raid. You can raid and fight other players. Modded is its browser category, where plugins or settings change the game. Oxide plugins are in use. Anti-cheat: VAC from Valve is enabled.
A procedural map of 1,000 with seed 6738, generated by the game, runs on typical test. RustMaps shows it from this page, since equal size and seed give an equal map.
Nothing on typical test states a region. Where the machine stands is not checked by Rust Live Stats; only the location a server states is shown. 104.153.151.75:28015 is its address.
Server fps averaged 240 over the last 48 hours, with a low of 239. Entity count reached 3,864: buildings, deployables and the rest of the world. The highest memory usage was 1,472 MB. Players experience lag when fps is low and the entity count climbs.
The setup on typical test is Rust network protocol 2635 and build 168909 with Linux. To join, your game must use the same protocol; Steam handles the update for you.
Right now typical test is online. About 29 hours ago is when it last restarted, according to its uptime. 24 of 24 hours were online in the last 1 full day, giving 100% uptime. Rust Live Stats has tracked it since 26 October 2026.
Enter client.connect 104.153.151.75: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.