On the class lists: C− (56), with population over 48 hours and no performance mark.
Players now0/ 200% full
7-day average0peak 2
Rank#5,007top 23%
Last wipe13m agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 0 of 20 on average. Plenty of space to grow.
Standingrank on player hours
77/ 100
B
Holds a respectable place: #5,007 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 92 server fps on average.
Wipeskeeping the crowd after a wipe
50/ 100
D
Keeps a fair share of its players through a wipe: 50% of wipes kept half their crowd.
Momentumrank now against a week ago
55/ 100
C−
Moving up: up 537 places this week.
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
PlayersWipe
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 23% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
5 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
WW·F···
·······
·······
·······
·W·W
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap2.4 daysbetween real wipes
on rhythm50%of its recent wipes
wipe-day peak1players, last three wipes
crowd held50%else halves by day 9
The first 48 hours of its last wipes
Tue 27 OctThu 1 OctTue 29 Sep
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 29 Oct, 08:44 UTC13m ago
–
–
running
0
Tue 27 Oct, 00:50 UTC2d ago
1
✓ held half
2.3 days
0
Thu 1 Oct, 17:10 UTCFW27d ago
1
halved by day 9
25.3 days
3
Tue 29 Sep, 06:22 UTC30d ago
1
✓ held half
2.5 days
0
Mon 28 Sep, 08:22 UTC31d ago
1
–
0.9 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
classmates: the same kind of game, then region, group limit, rate and wipes
Salty Test #1 leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 194.69.160.182:28015.
Is Salty Test #1 up, and how steady is its uptime?
Right now, Salty Test #1 is online. According to its reported uptime, the last restart was about 2 days 6 hours ago. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. It was first seen by Rust Server Score on 13 September 2026.
Is Salty Test #1 smooth to play on?
It never fell below 20 server fps in the last 48 hours, averaging 92. At its peak, it held 91,914 entities, including buildings, deployables and all else in the world. Up to 8,705 MB of memory was used. Lag is what players feel when fps is low and the entity count climbs.
What Rust version is Salty Test #1 on?
The server Salty Test #1 is on Rust network protocol 2635 and build 169621 under Linux. You need the same protocol to join; Steam takes care of updating your game.
Resets
When does Salty Test #1 wipe, and how often?
There is no next wipe to predict on Salty Test #1, as it wipes at irregular times. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 13 minutes.
What should you expect from wipe day on Salty Test #1?
Recent wipes have peaked at 1 players on average. 1 hours after the latest wipe began, the crowd hit its peak. Above half the peak until the next wipe: that was the pattern in 50% of its recent wipes. The crowd dropped below half by day 9 in the wipes where it did not hold.
Player numbers
What position does Salty Test #1 hold in the rankings?
Over the last seven days, Salty Test #1 has #5,007 for player hours, in the top 23% of all ranked servers.
What does the population on Salty Test #1 look like?
With 20 slots available, Salty Test #1 currently has 0 players. It peaked at 2 and averaged 0 players over the last seven days. The busiest time in the last 48 hours was 10:00 UTC, with an average of 1 players.
Tags and filters
What do Salty Test #1's tags stand for?
You'll see Salty Test #1 tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; 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; cs169621 (Build): The game build is 169621; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): Plugin framework: Carbon in the browser, which picks them up from the server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature Salty Test #1?
These Rust Server Score lists count Salty Test #1 among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 24 hours.
Server rules
How is Salty Test #1 set up, and what rules does it keep?
Nothing in the name of Salty Test #1 states a gather rate. The default of 8 players applies as the group cap. It runs survival, gather, build and raid, as in 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. The plugin count runs to Carbon. The server runs Valve's anti-cheat, VAC.
Salty Test #1 runs which map?
The game generates the procedural map on Salty Test #1 at size 4,500 with seed 1337. Because size and seed match, the map is the same each time, and this page links to it on RustMaps. The name of the map reads: Custom Map.
Getting in
What is the way to join Salty Test #1?
Enter client.connect 194.69.160.182:28015 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,cs169621,ts8,^z,^y
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
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.
cs169621
BuildThe game build is 169621.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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).