On the class lists: C− (56), with population over 48 hours and no performance mark.
Players now0/ 200% full
7-day average0peak 3
Rank#5,981top 27%
Last wipe25d 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: 0 of 20 on average. Plenty of space to grow.
Standingrank on player hours
73/ 100
B−
Holds a respectable place: #5,981 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: 186 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
53/ 100
D
Moving up: up 359 places this week.
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 23 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 27% 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 peak3players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 29 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 3 Oct, 06:11 UTC25d ago
3
–
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
You'll find no region listed by locServ47. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 85.236.190.20:28015 is the address to use.
How dependable is locServ47, and is it online at the moment?
You can join now: locServ47 is online. According to its reported uptime, the last restart was about 4 days 17 hours ago. It was up 144 of 168 hours over the last 7 full days, which is 86% of the time. On 23 September 2026, Rust Server Score saw it for the first time.
Is locServ47 smooth to play on?
The average over the last 48 hours was 186 server fps, and it never went below 143. Up to 48,485 entities were in the world, covering buildings, deployables and the rest. Up to 2,206 MB of memory was used. Lag is what players feel when fps is low and the entity count climbs.
What Rust version is locServ47 on?
Rust network protocol 2635 and build 168909 on Linux is what locServ47 runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
On what schedule does locServ47 reset?
There are too few wipes on record for locServ47 to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 25 days 18 hours.
What happens on locServ47 when wipe day arrives?
The average peak on its recent wipes was 3 players. 29 hours after the latest wipe began, the crowd hit its peak.
Population
Where does locServ47 sit among Rust servers?
Over the last seven days, locServ47 has #5,981 for player hours, in the top 27% of all ranked servers.
How many players does locServ47 usually have?
locServ47 is showing 0 players right now, with 20 slots in total. The seven-day average is 0 players, with a peak of 3. Over the last 48 hours, the peak hour was 07:00 UTC, averaging 1 players.
Lists and filters
How should you read the tags on locServ47?
You'll see locServ47 tagged with gmvanilla (Game mode): Survival, vanilla style; mp20 (Max players): 20 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does locServ47 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count locServ47 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.
Map and rules
How is locServ47 set up, and what rules does it keep?
The name of locServ47 gives no gather rate. 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. Raiding and PvP are both permitted. You will see it in the Community section of the server browser, since it is a community server. You are covered by VAC, Valve's anti-cheat.
locServ47 runs which map?
A procedural map of size 3,000 and seed 3221155, generated by the game, is what locServ47 runs. 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 locServ47?
To connect, start Rust, press F1, and type client.connect 85.236.190.20:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp20,ptrak,$r?,v2635,gmvanilla,cs168909,ts8
Game
gmvanilla
Game modeSurvival, vanilla style.
mp20
Max players20 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$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).