On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 400% full
7-day average0peak –
Rank#15,284top 69%
Last wipe28d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 40 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,284 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
50/ 100
D
Slows down under load at times: 30 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
50/ 100
D
Holding steady: down 105 places this week.
A term to build on.
Strongest in uptime (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 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
W······
·······
····W··
·······
·······
·······
·····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
usual gap17.1 daysbetween real wipes
wipe-day peak0players, last three wipes
The first 48 hours of its last wipes
Fri 2 OctMon 14 Sep
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 2 Oct, 00:23 UTC28d ago
0
–
running
0
Mon 14 Sep, 23:02 UTC45d ago
0
–
17.1 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
No region is published for A Rust Server. Rust Server Score takes the server's word for its location and does not trace the hardware. 64.40.8.189:30015 is the address to use.
How reliable is A Rust Server, and is it up?
You can join now: A Rust Server is online. About 4 days 1 hours ago, it restarted, based on the uptime it reports. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
How well does A Rust Server run?
It averaged 30 server fps over the last 48 hours, with a low of 30. Up to 107,623 entities were in the world, covering buildings, deployables and the rest. Up to 7,478 MB of memory was used. Players feel lag when fps drops and entities pile up.
Which Rust version is A Rust Server running?
You will find A Rust Server on Rust network protocol 2635 and build 168909, hosted on Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
When does A Rust Server wipe, and how often?
There are too few wipes on record for A Rust Server to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 28 days.
What happens on A Rust Server when wipe day arrives?
Across its recent wipes, the busiest moments averaged 0 players. 0 hours after the latest wipe began, the crowd hit its peak.
Player numbers
What position does A Rust Server hold in the rankings?
Over the last seven days, A Rust Server has #15,284 for player hours, in the top 69% of all ranked servers.
Is A Rust Server a busy server?
A Rust Server is showing 0 players right now, with 40 slots in total. Over the past seven days, the average player count was 0.
Tags
What is meant by the tags on A Rust Server?
gmrust (Game mode): Survival in the standard Rust style; mp40 (Max players): The server holds 40 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $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): Carbon provides the plugin framework here; ^x (Unknown flag): No documentation from Facepunch covers this flag are the tags A Rust Server publishes, and the game's server browser reads them. 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 A Rust Server?
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.
Server rules
How is A Rust Server set up, and what rules does it keep?
You will find no gather rate in the name of A Rust Server. The default of 8 players applies as the group cap. It runs survival, 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. You are not covered by VAC, Valve's anti-cheat.
Can you tell me which map A Rust Server uses?
A Rust Server runs a game-generated procedural map at size 5,000, seed 121212. 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.
Connecting
What is the way to join A Rust Server?
To connect, start Rust, press F1, and type client.connect 64.40.8.189:30015. 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,^z,^y,^x,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp40
Max playersThe server holds 40 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$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
CarbonCarbon provides the plugin framework here.
Other
^x
Unknown flagNo documentation from Facepunch covers this flag.
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 uptime (A); population is the one to work on (F).