Salty Test #2
194.69.160.182:28025 checked 7m ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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.
Rank
daily · 1 is bestTop 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Wed 30 Sep, 17:00 UTC14d ago | 1 | – | running | 1 |
| Tue 29 Sep, 09:24 UTC15d ago | 1 | – | 1.3 days | 0 |
| Mon 28 Sep, 13:00 UTC16d ago | 1 | – | 0.8 days | 0 |
| Tue 22 Sep, 16:16 UTC22d ago | 0 | – | 5.9 days | 0 |
| Mon 21 Sep, 21:35 UTC22d ago | 1 | – | 0.8 days | 0 |
| Mon 21 Sep, 01:59 UTC23d ago | 1 | – | 0.8 days | 1 |
| Sun 20 Sep, 19:41 UTC23d ago | 1 | – | 0.3 days | 1 |
| Sat 19 Sep, 18:19 UTC24d ago | 1 | – | 1.1 days | 0 |
| Sat 19 Sep, 00:15 UTC25d ago | 1 | – | 0.8 days | 1 |
| Fri 18 Sep, 13:02 UTC26d ago | 1 | – | 0.5 days | 0 |
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.
Similar servers
Quick answers
Rules and settings
Which settings and rules apply on Salty Test #2?
There is no gather rate in the name Salty Test #2. The group cap is 8 players, the default for the game. survival is the game mode, gather, build and raid: the standard game. Raiding and fighting other players are allowed. The server browser lists it under Modded: the game is changed by plugins or settings. Carbon plugins are running on it. VAC, Valve's anti-cheat, is switched on.
What is the map on Salty Test #2?
Size 3,500, seed 1337, generated by the game: the procedural map on Salty Test #2. You can view it on RustMaps from this page, since the same size and seed give the same map. The name of its map: Custom Map.
Server population
What is the population like on Salty Test #2?
The server Salty Test #2 is currently at 0 players out of 20 slots. Its seven-day average stands at 0 players.
What position does Salty Test #2 hold in the server rankings?
In the top 72% of ranked servers, Salty Test #2 holds #15,913 for player hours over the last seven days.
Lists and tags
What do Salty Test #2's tags indicate?
What the game's server browser gets from Salty Test #2 is this tag list: gmrust (Game mode): Survival in the standard Rust mode; mp20 (Max players): The server has 20 slots; ts8 (Group limit): The team cap is 8, which is the game's default; v2634 (Protocol): You'll need protocol 2634 on your game to join; cs167781 (Build): Build number: 167781; ptrak (Networking): Standard RakNet networking is in use here; $r? (Region code): No region code is set; ^z (Modded): Modded category: the game is altered by plugins or settings; ^y (Carbon): This server uses Carbon for plugins. Also in the tags: its players now, its queue and the time its world was made, and the top of this page shows them.
Which Rust Zerg Life filters and lists cover Salty Test #2?
The Rust Zerg Life lists that include Salty Test #2 are Modded Rust servers for clans and zergs. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Server info
What is the uptime and reliability of Salty Test #2?
Right now, Salty Test #2 is online. Based on the uptime it reports, the last restart was about 8 hours ago. Over the last 7 full days, uptime was 100%: 168 hours up out of 168. Its first appearance in Rust Zerg Life records is 17 September 2026.
How well does Salty Test #2 perform?
Over the past 48 hours, server fps averaged 59 and never dropped below 37. The world held as many as 80,360 entities, including buildings, deployables and everything else. The maximum memory it used was 4,092 MB. A climbing entity count and low fps are the source of the lag players feel.
Which Rust build does Salty Test #2 use?
Rust network protocol 2634 and build 167781 is what Salty Test #2 runs, on Linux. You can only join if your game uses the same protocol, and Steam takes care of updating it.
Where can you find Salty Test #2?
No region is published by Salty Test #2. The location shown by Rust Zerg Life is what a server says; it does not check where the machine stands. You can reach it at 194.69.160.182:28025.
Wipe cycle
What can you expect on wipe day on Salty Test #2?
At their busiest, its recent wipes drew an average of 1 players. 0 hours after the latest wipe, the crowd peaked.
How often does Salty Test #2 wipe, and on what days?
No next wipe can be predicted for Salty Test #2 because it wipes at irregular times. Next on Thursday 5 November at 19:00 UTC: the monthly force wipe that every Rust server gets. 14 days ago is when its present world was created.
Connect
What steps do I take to join Salty Test #2?
Enter client.connect 194.69.160.182:28025 in the F1 console. Another way: use Launch Rust on this page, which opens Rust through Steam and connects you.
Server tags
Published as mp20,ptrak,$r?,v2634,gmrust,cs167781,ts8,^z,^y
Game
gmrust
mp20
ts8
v2634
cs167781
ptrak
$r?
Mods and access
^z
^y
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.