On the class lists: F (38), with population over 48 hours and no performance mark.
Players now2/ 405% full
7-day average2peak 5
Rank#4,732top 21%
Last wipe2d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
5/ 100
F
A quiet classroom so far: 2 of 40 on average. Plenty of space to grow.
Standingrank on player hours
79/ 100
B
Holds a respectable place: #4,732 on player hours.
Uptimehours on the list, last 48
8/ 100
F
Attendance needs work: on the list only 4 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 224 server fps on average.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
100/ 100
A+
Climbing fast: up 9,707 places this week.
A term to build on.
Strongest in performance (A+); wipes are 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
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
AveragePeakWipe
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Server fpsWipe
EntitiesWipe
Memory, MBWipe
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 26 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 21% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
10 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
···FWW·
·······
W·W··W·
····W··
WW··
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 rhythm25%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 1
The first 48 hours of its last wipes
Mon 26 OctFri 23 OctSat 17 Oct
Players each hour, from the hour of the wipe. The latest peaked at 5, 5 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Tue 27 Oct, 06:01 UTC1d ago
–
–
running
1
Mon 26 Oct, 09:55 UTC2d ago
5
–
0.8 days
1
Fri 23 Oct, 16:12 UTC5d ago
1
–
2.7 days
0
Sat 17 Oct, 14:01 UTC11d ago
1
halved by day 1
6.1 days
1
Wed 14 Oct, 13:54 UTC14d ago
1
–
3 days
0
Mon 12 Oct, 11:48 UTC16d ago
1
halved by day 1
2.1 days
0
Sat 3 Oct, 15:41 UTC25d ago
6
halved by day 1
8.8 days
1
Sat 3 Oct, 08:00 UTC25d ago
6
–
0.3 days
0
Fri 2 Oct, 19:38 UTC26d ago
6
–
0.5 days
0
Thu 1 Oct, 19:44 UTCFW27d ago
6
–
1 days
0
Sun 27 Sep, 10:00 UTC31d ago
1
✓ held half
4.4 days
2
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
A Rust Server leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 57.128.229.173:25570.
Is A Rust Server up, and how steady is its uptime?
At this moment, A Rust Server is offline; the last time it was seen was 38 hours ago. The uptime it reports puts the last restart at about 50 minutes ago. It was up 15% of the time over the last 7 full days, 25 of 168 hours. The first sighting by Rust Server Score was on 26 September 2026.
Does A Rust Server perform well?
It averaged 224 server fps over the last 48 hours, with a low of 224. At its peak, it held 197,793 entities, including buildings, deployables and all else in the world. Memory use reached up to 3,223 MB. Players feel lag when fps drops and entities pile up.
On what Rust version does A Rust Server sit?
The server A Rust Server is on Rust network protocol 2635 and build 168909 under Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does A Rust Server reset?
There is no next wipe to predict on A Rust Server, as it wipes at irregular times. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 2 days 19 hours have passed since this world was made.
What should you expect from wipe day on A Rust Server?
Recent wipes have peaked at 2 players on average. Peak numbers came 5 hours into the latest wipe. Half the peak held until the next wipe in 0% of its recent wipes. The crowd dropped below half by day 1 in the wipes where it did not hold.
Player numbers
What position does A Rust Server hold in the rankings?
In the top 21% of all ranked servers, A Rust Server sits at #4,732 for player hours over the last seven days.
How many players does A Rust Server usually have?
A Rust Server is offline at the moment; the last time it was seen was 38 hours ago. It peaked at 5 and averaged 2 players over the last seven days. The busiest time in the last 48 hours was 13:00 UTC, with an average of 2 players.
Tags and filters
How should you read the tags on A Rust Server?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp40 (Max players): 40 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $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 are the tags A Rust Server publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does A Rust Server appear in the Rust Server Score lists and filters?
Rust Server Score lists that include A Rust Server: 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 3 days.
Rules and settings
What settings and rules apply on A Rust Server?
You will find no gather rate in the name of A Rust Server. With no change from the game default, groups take up to 8 players. survival is the mode here, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Carbon. The server does not run VAC, Valve's anti-cheat.
Which map is in play on A Rust Server?
A procedural map of size 6,000 and seed 1, generated by the game, is what A Rust Server runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
How do you get onto A Rust Server?
To connect, start Rust, press F1, and type client.connect 57.128.229.173:25570. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp40,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp40
Max players40 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$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 term to build on. Strongest in performance (A+); wipes are the one to work on (F).