On the class lists: F (39), with population over 48 hours and no performance mark.
Players now0/ 100% full
7-day average1peak 1
Rank#7,110top 32%
Last wipe13d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
7/ 100
F
A quiet classroom so far: 1 of 10 on average. Plenty of space to grow.
Standingrank on player hours
68/ 100
C+
Working its way up from the back of the class: #7,110 on player hours.
Uptimehours on the list, last 48
33/ 100
F
Attendance needs work: on the list only 16 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 240 server fps on average.
Wipeskeeping the crowd after a wipe
50/ 100
D
Keeps a fair share of its players through a wipe: 50% of wipes kept half their crowd.
Momentumrank now against a week ago
37/ 100
F
Slipped a little: down 1,830 places this week. Nothing a good wipe can't fix.
A term to build on.
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
No five-minute samples in the last two hours.
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 19 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 32% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
4 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
W······
··W····
·W·····
···W···
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap9 daysbetween real wipes
on rhythm67%of its recent wipes
wipe-day peak1players, last three wipes
crowd held50%else halves by day 8
The first 48 hours of its last wipes
Thu 15 OctTue 6 OctWed 30 Sep
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 15 Oct, 20:12 UTC13d ago
1
–
running
0
Tue 6 Oct, 12:20 UTC22d ago
1
halved by day 8
9.3 days
0
Wed 30 Sep, 17:39 UTC28d ago
0
–
5.8 days
1
Mon 21 Sep, 17:07 UTC37d ago
1
✓ held half
9 days
1
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 Local Server1 MAIN. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 86.146.176.163:28015.
Is Local Server1 MAIN up, and how steady is its uptime?
At this moment, Local Server1 MAIN is offline; the last time it was seen was 19 hours ago. The uptime it reports puts the last restart at about 5 hours ago. For the last 7 full days, it was up 21 of 168 hours, or 12% of the time. The first sighting by Rust Server Score was on 17 September 2026.
How well does Local Server1 MAIN run?
The average over the last 48 hours was 240 server fps, and it never went below 235. At its peak, it held 7,993 entities, including buildings, deployables and all else in the world. Memory use reached up to 1,411 MB. Players feel lag when fps drops and entities pile up.
Which Rust version is Local Server1 MAIN running?
Rust network protocol 2635 and build 168909 on Windows is what Local Server1 MAIN runs. Steam updates your game for you, but you need the same protocol to join.
Resets
How frequently does Local Server1 MAIN wipe its map?
Local Server1 MAIN wipes at times that vary, so no next wipe can be predicted. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 13 days 14 hours have passed since this world was made.
What happens on Local Server1 MAIN when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. 0 hours after the latest wipe began, the crowd hit its peak. Half the peak held until the next wipe in 50% of its recent wipes. Day 8 is when it sank below half in the wipes that did not hold.
Player numbers
Where does Local Server1 MAIN sit among Rust servers?
In the top 32% of all ranked servers, Local Server1 MAIN sits at #7,110 for player hours over the last seven days.
Is Local Server1 MAIN a busy server?
It has been 19 hours since Local Server1 MAIN was last seen, and it is offline right now. Averaging 1 players over seven days, it peaked at 1. The highest average in the last 48 hours came at 13:00 UTC, with 1 players.
Lists and filters
What do Local Server1 MAIN's tags stand for?
The game's browser takes its cue from the tags Local Server1 MAIN has set: gmrust (Game mode): Rust survival, played by the standard rules; mp10 (Max players): Its slot count is 10; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature Local Server1 MAIN?
These Rust Server Score lists count Local Server1 MAIN among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Map and rules
Which rules does Local Server1 MAIN enforce, and what are its settings?
Nothing in the name of Local Server1 MAIN states a gather rate. 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. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map Local Server1 MAIN uses?
A procedural map of size 1,500 and seed 9876513, generated by the game, is what Local Server1 MAIN runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
How should you connect to Local Server1 MAIN?
To connect, start Rust, press F1, and type client.connect 86.146.176.163:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp10
Max playersIts slot count is 10.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
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 term to build on. Strongest in performance (A+); population is the one to work on (F).