Salty Test #2
194.69.160.182:28025 checked 11m 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
Top 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
- usual gap
- 0.8 days between real wipes
- on rhythm
- 50% of its recent wipes
- wipe-day peak
- 1 players, last three wipes
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
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Wed 30 Sep, 17:00 UTC 13d ago | 1 | – | running | 1 |
| Tue 29 Sep, 09:24 UTC 15d ago | 1 | – | 1.3 days | 0 |
| Mon 28 Sep, 13:00 UTC 15d ago | 1 | – | 0.8 days | 0 |
| Tue 22 Sep, 16:16 UTC 21d ago | 0 | – | 5.9 days | 0 |
| Mon 21 Sep, 21:35 UTC 22d ago | 1 | – | 0.8 days | 0 |
| Mon 21 Sep, 01:59 UTC 23d ago | 1 | – | 0.8 days | 1 |
| Sun 20 Sep, 19:41 UTC 23d ago | 1 | – | 0.3 days | 1 |
| Sat 19 Sep, 18:19 UTC 24d ago | 1 | – | 1.1 days | 0 |
| Sat 19 Sep, 00:15 UTC 25d ago | 1 | – | 0.8 days | 1 |
| Fri 18 Sep, 13:02 UTC 25d 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
Population
Salty Test #2 ranking: what position does it hold?
Rank #15,948 over the last seven days in player hours: Salty Test #2, inside the top 72% of ranked servers.
How many players are on Salty Test #2?
Salty Test #2: 0 players now, with 20 slots available. The average player count over the last seven days is 0.
Tags and Filters
Salty Test #2 tags: what do they indicate?
For Salty Test #2, the game's server browser reads the following tags: gmrust (Game mode): Survival as standard in Rust; mp20 (Max players): The server has 20 slots; ts8 (Group limit): The game default is 8 per team; v2634 (Protocol): Your game must be on protocol 2634 to connect; cs167781 (Build): Running build 167781; ptrak (Networking): RakNet is the network layer in use; $r? (Region code): No region code listed; ^z (Modded): Under Modded, because plugins or settings modify play; ^y (Carbon): Uses Carbon for plugins. Current players, queue and world creation time come from the tags and appear at the top of this page.
Which lists and filters on BestRustServers.xyz contain Salty Test #2?
These BestRustServers.xyz lists include Salty Test #2: Best modded Rust servers. On the server list, the filters that bring it up are: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Server Information
Salty Test #2 Rust version: which one?
Rust network protocol 2634 and build 167781 on Linux is what Salty Test #2 uses. Joining requires the same protocol; Steam updates your game for you.
Is the performance on Salty Test #2 smooth?
Over 48 hours, it averaged 59 server fps; the lowest was 37. Buildings, deployables and the rest of the world accounted for up to 80,360 entities. Memory use peaked at 4,092 MB. Players feel lag when fps is low and entity count climbs.
What is the uptime and reliability of Salty Test #2?
The server is online: Salty Test #2. According to its reported uptime, the last restart was about 1 hours ago. It was up 100% of the time over the last 7 full days, 168 of 168 hours. The first time BestRustServers.xyz saw it was on 17 September 2026.
What is the location of Salty Test #2?
There is no region published by Salty Test #2. BestRustServers.xyz does not look up where the machine stands; it shows where a server says it is. 194.69.160.182:28025 is its address.
Settings & Map
What is the map on Salty Test #2?
A procedural map of size 3,500 and seed 1337 is what Salty Test #2 runs, generated by the game. The map can be viewed on RustMaps from this page, since size and seed fix it. Map: Custom Map.
What rules and configuration does Salty Test #2 have?
No gather rate appears in the name of Salty Test #2. The default cap of 8 players per group is in force. Listed as survival, gather, build, raid: the standard game. Fighting and raiding between players are allowed. Plugins or settings change the game, so it appears under Modded. Plugins in use: Carbon. VAC protection is on.
Wipe Cycle
On what schedule does Salty Test #2 wipe?
No next wipe can be predicted for Salty Test #2, which wipes at irregular times. The monthly force wipe applies to every Rust server, and the next is on Thursday 5 November at 19:00 UTC. The current world has been running since 13 days 17 hours.
What happens on wipe day on Salty Test #2?
The average busiest point of its recent wipes was 1 players. 0 hours into the latest wipe, the crowd reached its peak.
Join Server
What is the process to join Salty Test #2?
Use the F1 console: client.connect 194.69.160.182:28025. Launch Rust on this page does the same by opening Rust through Steam and connecting.
Server tags
Published as mp20,ptrak,$r?,v2634,gmrust,cs167781,ts8,^z,^y
Game
gmrust- Game mode Survival as standard in Rust.
mp20- Max players The server has 20 slots.
ts8- Group limit The game default is 8 per team.
v2634- Protocol Your game must be on protocol 2634 to connect.
cs167781- Build Running build 167781.
ptrak- Networking RakNet is the network layer in use.
$r?- Region code No region code listed.
Mods and access
^z- Modded Under Modded, because plugins or settings modify play.
^y- Carbon Uses Carbon for plugins.
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.