On the class lists: C (60), with population over 48 hours and no performance mark.
Players now1/ 502% full
7-day average1peak 6
Rank#3,953top 18%
Last wipe5d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 1 of 50 on average. Plenty of space to grow.
Standingrank on player hours
82/ 100
B+
Holds a respectable place: #3,953 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: 106 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
unmarked
–
No rank a week ago to compare with.
A steady term.
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 24 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 18% 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 peak6players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 6, 31 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 23 Oct, 23:48 UTC5d ago
6
–
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
No region is published for RustServer_5018. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 133.88.106.75:28015.
How dependable is RustServer_5018, and is it online at the moment?
The server is up: RustServer_5018 is online now. According to its reported uptime, the last restart was about 5 days 12 hours ago. For the last 5 full days, it was up 119 of 120 hours, or 99% of the time. It was first seen by Rust Server Score on 23 October 2026.
How well does RustServer_5018 run?
The average over the last 48 hours was 106 server fps, and it never went below 73. Up to 50,943 entities were in the world, covering buildings, deployables and the rest. Up to 2,535 MB of memory was used. Lag is what players feel when fps is low and the entity count climbs.
What Rust version is RustServer_5018 on?
Rust network protocol 2635 and build 168909 on Linux is what RustServer_5018 runs. To join, your game must use the same protocol; Steam handles the update.
Resets
How frequently does RustServer_5018 wipe its map?
The record holds too few of RustServer_5018's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 5 days 13 hours.
What should you expect from wipe day on RustServer_5018?
Across its recent wipes, the busiest moments averaged 6 players. 31 hours after the latest wipe began, the crowd hit its peak.
Player numbers
Where does RustServer_5018 sit among Rust servers?
In the top 18% of all ranked servers, RustServer_5018 sits at #3,953 for player hours over the last seven days.
What does the population on RustServer_5018 look like?
Right now, 1 players are on RustServer_5018, which has 50 slots. Averaging 1 players over seven days, it peaked at 6. The highest average in the last 48 hours came at 10:00 UTC, with 3 players.
Tags and filters
How should you read the tags on RustServer_5018?
gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): 50 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here are the tags RustServer_5018 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.
Which lists and filters on Rust Server Score show RustServer_5018?
Rust Server Score lists that include RustServer_5018: Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.
Rules and settings
Which rules does RustServer_5018 enforce, and what are its settings?
The name of RustServer_5018 gives no gather rate. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. Under Community in the server browser you will find this community server. The server runs Valve's anti-cheat, VAC.
Which map is in play on RustServer_5018?
The game generates the procedural map on RustServer_5018 at size 3,000 with seed 22314. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How should you connect to RustServer_5018?
Enter client.connect 133.88.106.75: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?,v2635,gmrust,cs168909,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max players50 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
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 steady term. Strongest in performance (A+); population is the one to work on (F).