On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 200% full
7-day average0peak 1
Rank#11,210top 50%
No wipesresets5 new worlds this week: a reset every few hours, not a wipe schedule
Next wipe–resets, no wipes
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 20 on average. Plenty of space to grow.
Standingrank on player hours
50/ 100
D
Working its way up from the back of the class: #11,210 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours
98/ 100
A+
Runs smoothly: 59 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
31/ 100
F
Lost ground: down 4,171 places this week. A strong wipe could turn it round.
A fair term, with more to come.
Strongest in performance (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 best
RankRank in region
Top 50% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
a new world every few hours
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
WWWW·WW
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
World resets
a new world every few hours; none of these counts as a wipe
Wiped
Peak
Crowd
Lasted
Players before
Sun 25 Oct, 00:30 UTC4d ago
–
–
–
0
Sat 24 Oct, 23:13 UTC4d ago
–
–
–
0
Thu 22 Oct, 18:54 UTC6d ago
–
–
–
0
Thu 22 Oct, 15:36 UTC6d ago
–
–
–
0
Thu 22 Oct, 15:15 UTC6d ago
–
–
–
1
Wed 21 Oct, 18:57 UTC7d ago
–
–
–
1
Wed 21 Oct, 18:22 UTC7d ago
–
–
–
1
Wed 21 Oct, 16:48 UTC7d ago
–
–
–
1
Wed 21 Oct, 16:07 UTC7d ago
–
–
–
0
Tue 20 Oct, 23:47 UTC8d ago
–
–
–
1
Tue 20 Oct, 22:57 UTC8d ago
–
–
–
1
Tue 20 Oct, 22:34 UTC8d ago
–
–
–
1
Tue 20 Oct, 21:43 UTC8d ago
–
–
–
1
Tue 20 Oct, 20:29 UTC8d ago
–
–
–
1
Tue 20 Oct, 19:35 UTC8d ago
–
–
–
1
Tue 20 Oct, 19:05 UTC8d ago
–
–
–
1
Tue 20 Oct, 18:37 UTC8d ago
–
–
–
1
Tue 20 Oct, 18:08 UTC8d ago
–
–
–
1
Mon 19 Oct, 18:58 UTC9d ago
–
–
–
0
Mon 19 Oct, 16:23 UTC9d ago
–
–
–
1
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
No region is published for Salty Test #2. Rust Server Score takes the server's word for its location and does not trace the hardware. 194.69.160.182:28025 is the address to use.
How reliable is Salty Test #2, and is it up?
You can join now: Salty Test #2 is online. The uptime it reports puts the last restart at about 4 days 9 hours ago. For the last 7 full days, it was up 167 of 168 hours, or 99% of the time. On 17 September 2026, Rust Server Score saw it for the first time.
Is Salty Test #2 smooth to play on?
It averaged 59 server fps over the last 48 hours, with a low of 43. Buildings, deployables and everything else in the world added up to as many as 90,000 entities. Up to 4,908 MB of memory was used. When fps is low and entities climb, that is lag to players.
What Rust version is Salty Test #2 on?
Rust network protocol 2635 and build 169075 on Linux is what Salty Test #2 runs. Steam updates your game for you, but you need the same protocol to join.
Resets
How frequently does Salty Test #2 wipe its map?
No resets count as wipes on Salty Test #2, because the world is remade every few hours and no schedule is kept.
Population
Where does Salty Test #2 place in the wider field of Rust servers?
Over the last seven days, Salty Test #2 has #11,210 for player hours, in the top 50% of all ranked servers.
Is Salty Test #2 a busy server?
Salty Test #2 is showing 0 players right now, with 20 slots in total. Averaging 0 players over seven days, it peaked at 1.
Tags and filters
What is meant by the tags on Salty Test #2?
The game's browser takes its cue from the tags Salty Test #2 has set: gmrust (Game mode): Survival in the standard Rust style; mp20 (Max players): 20 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs169075 (Build): The game build is 169075; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Plugin framework: Carbon. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does Salty Test #2 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Salty Test #2 among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
Rules and settings
How is Salty Test #2 set up, and what rules does it keep?
The name of Salty Test #2 gives no gather rate. With no change from the game default, groups take up to 8 players. It runs survival, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Carbon plugins are running on it. The server runs Valve's anti-cheat, VAC.
Which map is in play on Salty Test #2?
Salty Test #2 runs a game-generated procedural map at size 4,000, seed 1337. A matching size and seed produce the same map, viewable on RustMaps from this page. The name of the map reads: Custom Map.
How to join
How should you connect to Salty Test #2?
Enter client.connect 194.69.160.182:28025 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp20,ptrak,$r?,v2635,gmrust,cs169075,ts8,^z,^y
Game
gmrust
Game modeSurvival in the standard Rust style.
mp20
Max players20 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs169075
BuildThe game build is 169075.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonPlugin framework: Carbon.
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.
A fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).