On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak –
Rank#15,339top 69%
Last wipe8d 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
31/ 100
F
Working its way up from the back of the class: #15,339 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
100/ 100
A+
Runs smoothly: 95 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 166 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
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
Tue 20 Oct, 02:13 UTC8d 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_19781 leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 163.44.99.10:28015.
How reliable is RustServer_19781, and is it up?
Right now, RustServer_19781 is online. According to its reported uptime, the last restart was about 4 days 22 hours ago. It was up 100% of the time over the last 7 full days, 168 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
Does RustServer_19781 perform well?
It averaged 95 server fps over the last 48 hours, with a low of 75. At its peak, it held 46,059 entities, including buildings, deployables and all else in the world. Memory use reached up to 2,170 MB. When fps is low and entities climb, that is lag to players.
Which Rust version is RustServer_19781 running?
The server RustServer_19781 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 RustServer_19781 reset?
There are too few wipes on record for RustServer_19781 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. The world it runs now was created 8 days 20 hours.
What happens on RustServer_19781 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.
Population
Where does RustServer_19781 place in the wider field of Rust servers?
Over the last seven days, RustServer_19781 has #15,339 for player hours, in the top 69% of all ranked servers.
How many players does RustServer_19781 usually have?
With 50 slots available, RustServer_19781 currently has 0 players. For the last seven days, the average number of players was 0.
Tags
What is meant by the tags on RustServer_19781?
The game's browser takes its cue from the tags RustServer_19781 has set: gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): Its slot count is 50; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here. 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 lists and filters on Rust Server Score show RustServer_19781?
These Rust Server Score lists count RustServer_19781 among them: 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.
Rules and settings
Which rules does RustServer_19781 enforce, and what are its settings?
You will find no gather rate in the name of RustServer_19781. The default of 8 players applies as the group cap. It runs survival, gather and build and raid: 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.
Can you tell me which map RustServer_19781 uses?
A procedural map of size 3,000 and seed 16682, generated by the game, is what RustServer_19781 runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How do you get onto RustServer_19781?
Enter client.connect 163.44.99.10: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 modeSurvival in the standard Rust style.
mp50
Max playersIts slot count is 50.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThe game build is 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 fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).