On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak –
Rank#15,388top 70%
Last wipe11d 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 50 on average. Plenty of space to grow.
Standingrank on player hours
30/ 100
F
Working its way up from the back of the class: #15,388 on player hours.
Uptimehours on the list, last 48
98/ 100
A+
Excellent attendance: on the list 47 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 118 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
49/ 100
D
Slipped a little: down 158 places this week. Nothing a good wipe can't fix.
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 70% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····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.
wipe-day peak0players, last three wipes
The first 48 hours of its last wipes
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 16 Oct, 10:59 UTC11d ago
0
–
running
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
RustServer leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 162.43.4.36:28015 is the address to use.
How reliable is RustServer, and is it up?
Right now, RustServer is online. The uptime it reports puts the last restart at about 10 days 1 hours ago. For the last 7 full days, it was up 168 of 168 hours, or 100% of the time. The first sighting by Rust Server Score was on 13 September 2026.
Does RustServer perform well?
It never fell below 83 server fps in the last 48 hours, averaging 118. At its peak, it held 49,717 entities, including buildings, deployables and all else in the world. At its highest, it used 2,739 MB of memory. Players feel lag when fps drops and entities pile up.
What Rust version is RustServer on?
Rust network protocol 2634 and build 167781 on Linux is what RustServer runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does RustServer wipe its map?
RustServer has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 11 days 9 hours have passed since this world was made.
What happens on RustServer when wipe day arrives?
Across its recent wipes, the busiest moments averaged 0 players. Peak numbers came 0 hours into the latest wipe.
Player numbers
Where does RustServer sit among Rust servers?
Over the last seven days, RustServer has #15,388 for player hours, in the top 70% of all ranked servers.
Is RustServer a busy server?
RustServer is showing 0 players right now, with 50 slots in total. For the last seven days, the average number of players was 0.
Tags
What do RustServer's tags stand for?
gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set are the tags RustServer publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does RustServer appear in the Rust Server Score lists and filters?
Rust Server Score lists that include RustServer: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Server rules
Which rules does RustServer enforce, and what are its settings?
You will find no gather rate in the name of RustServer. The group limit stays at the game's default of 8 players. survival is the mode here, gather, build and raid, as in the standard game. You can raid other players and fight them. You will see it in the Community section of the server browser, since it is a community server. The server runs Valve's anti-cheat, VAC.
Can you tell me which map RustServer uses?
RustServer runs a game-generated procedural map at size 3,000, seed 19686. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Getting in
How do you get onto RustServer?
Enter client.connect 162.43.4.36: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 asmp50,ptrak,$r?,v2634,gmrust,cs167781,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max playersThe server holds 50 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
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).