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 51% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
The current map
Saturday 24 October 2026, 23:13 UTC
Wipe
Thursday 22 October 2026, 15:15 UTC
Wipe
Wednesday 21 October 2026, 16:07 UTC
Wipe
Tuesday 20 October 2026, 18:08 UTC
Wipe
Monday 19 October 2026, 15:49 UTC
Wipe
Friday 16 October 2026, 21:19 UTC
Wipe
Thursday 15 October 2026, 13:55 UTC
Wipe
Wednesday 30 September 2026, 17:00 UTC
Wipe
Tuesday 29 September 2026, 09:24 UTC
Wipe
Monday 28 September 2026, 13:00 UTC
Wipe
Tuesday 22 September 2026, 16:16 UTC
Wipe
Monday 21 September 2026, 21:35 UTC
Wipe
Monday 21 September 2026, 01:59 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.
Recent wipes on this server averaged a peak of 1 players at their busiest. Peak population on the latest wipe came 0 hours after it. In 0% of recent wipes, population held above half the peak right through to the next wipe. On those occasions it fell below half by day 1.
No next wipe can be predicted for Salty Test #2, which wipes at irregular times. 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 4 days 16 hours.
These are the Rust Live Stats lists Salty Test #2 fits: Modded Rust servers live now. These filters on the server list bring it up: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
The server browser reads gmrust (Game mode): Survival here follows standard Rust; mp20 (Max players): The slot count is 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; cs169075 (Build): The game build is 169075; ptrak (Networking): RakNet is the network layer — the game's standard one; $r? (Region code): No region code is set here; ^z (Modded): Plugins or settings changes put this under Modded; ^y (Carbon): The plugins run through Carbon, which Salty Test #2 publishes. Players now, queue length and world creation time are carried in the tags too, and appear at the top of this page.
Live now: 0 players on Salty Test #2, out of 20 slots. The seven-day average is 0 players, with a peak of 1.
Player hours over seven days put Salty Test #2 at #11,441, in the top 51% of all ranked servers.
No gather rate appears in the name Salty Test #2. The default applies: 8 players to a group. survival applies here, the standard game: gather, build, raid. Fighting and raiding between players are allowed. The server browser files it under Modded: plugins or settings alter the game. Carbon plugins are in use. VAC is enabled: Valve's anti-cheat.
Salty Test #2 runs a game-generated procedural map: size 4,000, seed 1337. RustMaps shows it from this page, since equal size and seed give an equal map. For the map name it lists Custom Map.
Nothing on Salty Test #2 states a region. A server's stated location is what Rust Live Stats shows; the machine's actual position is not looked up. 194.69.160.182:28025 is its address.
The average server fps was 59 over the last 48 hours; the lowest was 43. It supported up to 90,000 entities, covering buildings, deployables and all other objects. The highest memory usage was 4,908 MB. Lag, as players feel it, comes from low fps and a rising entity count.
Rust network protocol 2635 and build 169075 on Linux is what Salty Test #2 runs. Steam updates it for you, but your game needs the same protocol to join.
Salty Test #2 is up and running at this moment. The uptime it reports puts the last restart at about 4 days 14 hours ago. It was online for 167 of 168 hours in the last 7 full days, or 99% of the time. On 17 September 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 194.69.160.182:28025.