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 17 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
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.
Too few wipes are recorded for Test server to establish a pattern. 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 1574 days 7 hours.
These are the Rust Live Stats lists Test server fits: Live Rust community servers. Under the filters Type: Community (not modded, not official) and No plugins at all it appears on the server list.
These are the tags Test server makes public: gmrust (Game mode): Survival here follows standard Rust; mp100 (Max players): 100 slots are available; v2348 (Protocol): The server runs protocol 2348, so match that version to join; ptrak (Networking): The network layer is RakNet, the standard the game uses; h3de62e32 (Custom tag): You will not find this among Rust's standard tags: the owner or a plugin created it; stok (Custom tag): You will not find this among Rust's standard tags: the owner or a plugin created it. 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.
0 of Test server's 100 slots are filled right now. Averaged over seven days: 0 players.
Ranked by seven-day player hours, Test server is #15,327, placing it in the top 69% of ranked servers.
Nothing in the name of Test server states a gather rate. No group limit appears in its listing. survival is the mode, with the standard game: gather, build, raid. Raiding and player combat are both permitted. The server browser lists it under Community. Anti-cheat: VAC from Valve is enabled.
A procedural map of 4,500 with seed 1337, generated by the game, runs on Test server. Size and seed repeat the same map, so RustMaps can show it from this page.
There is no region from Test server. The location shown on Rust Live Stats is the one a server gives, not a lookup of the machine's position. 194.242.10.242:28215 is its address.
It never went below 7 server fps in the last 48 hours, averaging 23. It supported up to 3,427,029 entities, covering buildings, deployables and all other objects. The highest memory usage was 56,091 MB. Lag, as players feel it, comes from low fps and a rising entity count.
Rust network protocol 2348 on Windows is what Test server runs. To join, your game must use the same protocol; Steam handles the update for you.
Test server is up and running at this moment. Based on the uptime it reports, the last restart was about 9 days 19 hours ago. 167 of 168 hours were online in the last 7 full days, giving 99% uptime. On 13 September 2026, Rust Live Stats saw it for the first time.
Enter client.connect 194.242.10.242:28215 in the console (F1 in Rust). Another way is Launch Rust and join on this page: it opens Rust through Steam and connects you.