Salty Test #2
Online 194.69.160.182:28025 checked 10m 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 UTC13d ago | 1 | – | running | 1 |
| Tue 29 Sep, 09:24 UTC15d ago | 1 | – | 1.3 days | 0 |
| Mon 28 Sep, 13:00 UTC15d ago | 1 | – | 0.8 days | 0 |
| Tue 22 Sep, 16:16 UTC21d 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 UTC25d 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 wipes.
Quick answers
From the figures on this page.
Server tags
How should you read the tags on Salty Test #2?
gmrust (Game mode): Rust survival, the standard way; mp20 (Max players): 20 player slots; ts8 (Group limit): 8 to a team, as the game ships it; v2634 (Protocol): Protocol 2634: your game must match to get in; cs167781 (Build): It runs on build 167781; ptrak (Networking): The game's usual network layer, RakNet, is used; $r? (Region code): Region code not set; ^z (Modded): It sits in Modded: plugins or settings make the difference; ^y (Carbon): The plugin framework here is Carbon is what Salty Test #2 tags itself with, and the server browser takes note. Tags also carry its current players, its queue and when the world was made, all up top on this page.
Where does Salty Test #2 appear in the lists and filters on Rust Vending Machine?
These Rust Vending Machine lists include Salty Test #2: Modded Rust servers. It shows under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Settings and rules
What map is in play on Salty Test #2?
Salty Test #2 runs a procedural map of size 3,500 with seed 1337, generated by the game. You can view it on RustMaps from this page, since the same size and seed give the same map. You will see the map name as: Custom Map.
What rules does Salty Test #2 enforce, and what settings does it run?
There is no gather rate in the name Salty Test #2. 8 players is the default group size, and that is the cap here. You play survival, the usual game of gathering, building and raiding. You can fight and raid other players. Plugins or settings change the game, so it is listed under Modded. The plugins it runs number Carbon. The server has VAC, Valve's anti-cheat, switched on.
Server info
What is the location of Salty Test #2?
There is no region listed for Salty Test #2. Rust Vending Machine reports the location a server claims, not where the machine actually sits. Find it at this address: 194.69.160.182:28025.
What is the uptime like on Salty Test #2?
The shelves show Salty Test #2 in stock and online right now. Its uptime figure puts the last restart at roughly 2 hours ago. Over 7 full days, the shelves were stocked for 168 of 168 hours (100%). It came to Rust Vending Machine's notice on 17 September 2026.
How well does Salty Test #2 perform?
Over the last 48 hours the average server fps was 59, with a low of 37. Up to 80,360 entities were in play, buildings, deployables and the rest of the world combined. The highest memory reading was 4,092 MB. What players call lag comes from low fps and an entity count on the rise.
What version does Salty Test #2 use?
Rust network protocol 2634 and build 167781 on Linux is what powers Salty Test #2. The protocol has to line up on your side to join, and Steam does the updating.
Population
Where does Salty Test #2 sit in the rankings?
The last seven days of player hours place Salty Test #2 at #15,948, in the top 72% of all ranked servers.
How many players are on Salty Test #2 right now?
Right now 20 slots in Salty Test #2 hold 0 players. The seven-day average stands at 0 players.
Wipe details
On what schedule does Salty Test #2 wipe?
There is no way to predict the next wipe at Salty Test #2, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes, and every Rust server wipes. The world it has now started 13 days 18 hours ago.
What can you expect on Salty Test #2 when wipe day comes?
An average of 1 players turned up at the peak of its recent wipes. On the latest wipe, 0 hours after it began, the crowd peaked.
How to join
What steps do you take to join Salty Test #2?
Press F1 in Rust to bring up the console and enter client.connect 194.69.160.182:28025. Alternatively, the Launch Rust option on this page opens Rust via Steam and joins for 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.