On the class lists: D (45), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak 1
Rank#12,965top 58%
Last wipe18d 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
42/ 100
F
Working its way up from the back of the class: #12,965 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: 93 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
41/ 100
F
Slipped a little: down 2,229 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 11 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 58% 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
RustServer_4380 leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. 160.251.203.118:28015 is the address to use.
How reliable is RustServer_4380, and is it up?
You can join now: RustServer_4380 is online. About 7 days 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 10 October 2026.
Is RustServer_4380 smooth to play on?
It never fell below 68 server fps in the last 48 hours, averaging 93. At its peak, it held 53,140 entities, including buildings, deployables and all else in the world. Memory use reached up to 2,567 MB. Lag is what players feel when fps is low and the entity count climbs.
Which Rust version is RustServer_4380 running?
Rust network protocol 2635 and build 168909 on Linux is what RustServer_4380 runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
When does RustServer_4380 wipe, and how often?
The record holds too few of RustServer_4380's wipes to tell its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 18 days 23 hours have passed since this world was made.
Player numbers
Where does RustServer_4380 place in the wider field of Rust servers?
In the top 58% of all ranked servers, RustServer_4380 sits at #12,965 for player hours over the last seven days.
How many players does RustServer_4380 usually have?
RustServer_4380 is showing 0 players right now, with 50 slots in total. The seven-day average is 0 players, with a peak of 1. Over the last 48 hours, the peak hour was 06:00 UTC, averaging 0 players.
Tags and filters
What do RustServer_4380's tags stand for?
The game's browser takes its cue from the tags RustServer_4380 has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): The server holds 50 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): This runs on build 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this 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.
Where does RustServer_4380 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count RustServer_4380 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.
Rules and settings
How is RustServer_4380 set up, and what rules does it keep?
The name of RustServer_4380 gives no gather rate. The default of 8 players applies as the group cap. You get survival here, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map RustServer_4380 uses?
A procedural map of size 3,000 and seed 10219, generated by the game, is what RustServer_4380 runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How should you connect to RustServer_4380?
Enter client.connect 160.251.203.118: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 modeThis one runs plain Rust survival, with nothing altered.
mp50
Max playersThe server holds 50 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
BuildThis runs on build 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
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).