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 James Test Rust Server to establish a pattern. Thursday 5 November at 19:00 UTC is the next monthly force wipe, and no Rust server is spared it. 68 days 21 hours have passed since this world was generated.
These are the Rust Live Stats lists James Test Rust Server fits: Live Rust community servers. You will find it on the server list under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
gmrust (Game mode): Survival here follows standard Rust; mp20 (Max players): Slots: 20; ts8 (Group limit): Teams stop at 8, the default the game ships with; v2632 (Protocol): Join only if your game is on protocol 2632; cs161125 (Build): This server runs game build 161125; ptrak (Networking): The network layer is RakNet, the standard the game uses; $r? (Region code): Region code: none set: that is the tag list James Test Rust Server publishes for the game's server browser. Players now, queue length and world creation time are carried in the tags too, and appear at the top of this page.
James Test Rust 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, James Test Rust Server is #15,323, placing it in the top 69% of ranked servers.
The name James Test Rust Server carries no gather rate. The default applies: 8 players to a group. 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. VAC is enabled: Valve's anti-cheat.
Size 6,000, seed 2797370150: that is the procedural map the game generates for James Test Rust Server. Same size, same seed, same map: RustMaps has it, reachable from this page.
There is no region from James Test Rust Server. Where the machine stands is not checked by Rust Live Stats; only the location a server states is shown. Connect to 216.245.176.215:28015.
The average server fps was 30 over the last 48 hours; the lowest was 30. It supported up to 207,046 entities, covering buildings, deployables and all other objects. Up to 6,256 MB of memory was used. Players experience lag when fps is low and the entity count climbs.
The setup on James Test Rust Server is Rust network protocol 2632 and build 161125 with Windows. Steam updates it for you, but your game needs the same protocol to join.
At the time of this update, James Test Rust Server is live. About 9 days 19 hours ago is when it last restarted, according to its uptime. It was online for 167 of 168 hours in the last 7 full days, or 99% of the time. The first sighting by Rust Live Stats was on 13 September 2026.
Enter client.connect 216.245.176.215: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.