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 14 Oct. 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 Trents Test 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. The world you are playing on was built 14 days 16 hours.
On Rust Live Stats, Trents Test Server is listed under Live Rust community servers. These filters on the server list bring it up: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
These are the tags Trents Test Server makes public: gmrust (Game mode): Survival here follows standard Rust; mp50 (Max players): Slots: 50; ts8 (Group limit): Team cap: 8, which is the game default; v2634 (Protocol): You need protocol 2634 on your game to get in; cs167781 (Build): This server runs game build 167781; ptrak (Networking): The network layer is RakNet, the standard the game uses; $r? (Region code): The server sets no region code. The current player count, the queue and the world's creation time also sit in the tags, shown at the top of this page.
0 of Trents Test Server's 50 slots are filled right now. Averaged over seven days: 0 players.
Player hours over seven days put Trents Test Server at #15,426, in the top 69% of all ranked servers.
No gather rate appears in the name Trents Test Server. The default applies: 8 players to a group. survival applies here, 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.
A procedural map of 2,400 with seed 1337, generated by the game, runs on Trents Test Server. Same size, same seed, same map: RustMaps has it, reachable from this page. For the map name it lists Custom Map.
Nothing on Trents Test Server states a region. The location shown on Rust Live Stats is the one a server gives, not a lookup of the machine's position. Connect to 104.143.2.186:28015.
It never went below 188 server fps in the last 48 hours, averaging 231. It supported up to 12,444 entities, covering buildings, deployables and all other objects. The highest memory usage was 2,296 MB. Players experience lag when fps is low and the entity count climbs.
Rust network protocol 2634 and build 167781 on Windows is what Trents Test Server runs. To join, your game must use the same protocol; Steam handles the update for you.
At the time of this update, Trents Test Server is live. The uptime it reports puts the last restart at about 14 days 13 hours ago. 168 of 168 hours were online in the last 7 full days, giving 100% uptime. On 14 October 2026, Rust Live Stats saw it for the first time.
Use Launch Rust and join on this page to open Rust through Steam and connect, or start Rust, press F1, and type client.connect 104.143.2.186:28015.