Online194.69.160.182:28025checked 12m ago
Salty Test #2
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 UTC23d ago | 1 | – | 0.8 days | 0 |
| Mon 21 Sep, 01:59 UTC23d ago | 1 | – | 0.8 days | 1 |
| Sun 20 Sep, 19:41 UTC24d ago | 1 | – | 0.3 days | 1 |
| Sat 19 Sep, 18:19 UTC25d 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
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageRules, map and settings
What are the server rules for Salty Test #2?
A gather rate is absent from the name of Salty Test #2. Groups are capped at 8 players, the default in the game. survival is the game mode, gather, build, raid: the standard game. Fighting and raiding between players is allowed. The server browser lists it as Modded, with plugins or settings that alter the game. Plugins: Carbon. Anti-cheat VAC from Valve is on.
Which map is running on Salty Test #2?
A procedural map of size 3,500 is what Salty Test #2 runs, generated by the game with seed 1337. You can see it on RustMaps from this page, because the same size and seed give the same map. Its map is called: Custom Map.
Tags, lists and filters
Where can Salty Test #2 be found in Rust Player Count lists and filters?
These Rust Player Count lists include Salty Test #2: Modded Rust servers. You can find it on the server list using these filters: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
What information do the tags on Salty Test #2 convey?
These are the tags Salty Test #2 publishes for the game's server browser: gmrust (Game mode): The usual Rust survival experience; mp20 (Max players): The server has 20 slots; ts8 (Group limit): 8 per team, which is what the game sets by default; v2634 (Protocol): Your game version needs to be on protocol 2634 to connect; cs167781 (Build): The game build is 167781; ptrak (Networking): The network layer is RakNet, Rust's standard one; $r? (Region code): The region code field is empty; ^z (Modded): This server is Modded; plugins or settings affect how it plays; ^y (Carbon): It uses Carbon for plugins. At the top of this page, its tags show its current players, queue and world creation time as well.
Population
How many players does Salty Test #2 have?
Right now, 0 players are on Salty Test #2, which has 20 slots. The average player count for the past seven days is 0.
How does Salty Test #2 compare in server rankings?
Over the last seven days, Salty Test #2 is #15,912 for player hours, placing it in the top 72% of ranked servers.
Server details
What is the online status and reliability of Salty Test #2?
You can find Salty Test #2 online at the moment. Based on the uptime it reports, the last restart was about 12 hours ago. It was up 100% of the time over the last 7 full days, 168 of 168 hours. 17 September 2026 is when Rust Player Count first saw it.
What is the Rust version for Salty Test #2?
Rust network protocol 2634 and build 167781 on Linux is what Salty Test #2 uses. The protocol has to match for you to join, but Steam updates it without any action from you.
Where can you find Salty Test #2?
A region is not published by Salty Test #2. The location shown by Rust Player Count is the one a server provides; it does not verify where the machine actually is. You can reach it at 194.69.160.182:28025.
How well does Salty Test #2 perform?
In the last 48 hours, it averaged 59 server fps, with a low of 37. The highest entity count was 80,619, covering buildings, deployables and all other objects. At its highest, it used 4,255 MB of memory. A climbing entity count and low fps are felt as lag by players.
Wipe days
What happens on Salty Test #2 when a wipe occurs?
The average busiest point in recent wipes reached 1 players. 0 hours after the wipe, the crowd on the latest wipe was at its highest.
When does Salty Test #2 wipe?
Wipes on Salty Test #2 come at irregular times, leaving no next wipe to forecast. The monthly force wipe hits every Rust server, and on Thursday 5 November at 19:00 UTC it comes next. It has been running its current world for 14 days 5 hours.
Join the server
What steps are needed to join Salty Test #2?
Open the Rust console with F1, then type client.connect 194.69.160.182:28025. Alternatively, fit into the server through the Launch Rust button on this page; that starts Rust via Steam and joins you.
Server tags
what each one meansPublished 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.