On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak –
Rank#15,335top 69%
Last wipe102d agono schedule published
Next wipe–no wipe 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
31/ 100
F
Working its way up from the back of the class: #15,335 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: 201 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 210 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 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
You'll find no region listed by RustServer_22919. Rust Server Score takes the server's word for its location and does not trace the hardware. 163.44.100.211:28015 is the address to use.
How dependable is RustServer_22919, and is it online at the moment?
You can join now: RustServer_22919 is online. About 5 days 10 hours ago, it restarted, based on the uptime it reports. For the last 7 full days, it was up 167 of 168 hours, or 99% of the time. It was first seen by Rust Server Score on 13 September 2026.
Is RustServer_22919 smooth to play on?
The average over the last 48 hours was 201 server fps, and it never went below 114. At its peak, it held 48,714 entities, including buildings, deployables and all else in the world. Memory use reached up to 2,326 MB. Lag is what players feel when fps is low and the entity count climbs.
On what Rust version does RustServer_22919 sit?
Rust network protocol 2631 and build 158240 on Linux is what RustServer_22919 runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
How frequently does RustServer_22919 wipe its map?
There are too few wipes on record for RustServer_22919 to show a rhythm. 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 102 days 5 hours.
Player count
Where does RustServer_22919 sit among Rust servers?
Over the last seven days, RustServer_22919 has #15,335 for player hours, in the top 69% of all ranked servers.
What does the population on RustServer_22919 look like?
With 50 slots available, RustServer_22919 currently has 0 players. Over the past seven days, the average player count was 0.
Lists and filters
What do RustServer_22919's tags stand for?
You'll see RustServer_22919 tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2631 (Protocol): To get in, your game needs to be on the same version: the protocol is 2631; cs158240 (Build): Build number: 158240; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set in the browser, which picks them up from the server. 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_22919?
Rust Server Score lists that include RustServer_22919: Best community servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Rules and settings
What settings and rules apply on RustServer_22919?
The name of RustServer_22919 gives no gather rate. The default of 8 players applies as the group cap. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. You will see it in the Community section of the server browser, since it is a community server. VAC, Valve's anti-cheat, is enabled.
Which map is in play on RustServer_22919?
RustServer_22919 runs a game-generated procedural map at size 3,000, seed 20291. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
How should you connect to RustServer_22919?
To connect, start Rust, press F1, and type client.connect 163.44.100.211:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2631,gmrust,cs158240,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp50
Max playersThe server holds 50 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2631
ProtocolTo get in, your game needs to be on the same version: the protocol is 2631.
cs158240
BuildBuild number: 158240.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$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).