Working its way up from the back of the class: #16,009 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
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 944 places this week.
A term to build on.
Strongest in momentum (D); standing 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.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
······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.
usual gap9.8 daysbetween real wipes
wipe-day peak0players, last three wipes
The first 48 hours of its last wipes
Sun 4 OctThu 24 Sep
Players each hour, from the hour of the wipe. The latest peaked at 0, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 4 Oct, 12:28 UTC23d ago
0
–
running
0
Thu 24 Sep, 17:31 UTC33d ago
0
–
9.8 days
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
In what location does ANCHOR TEST - local stand sit?
ANCHOR TEST - local stand 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 95.105.76.2:28115.
How dependable is ANCHOR TEST - local stand, and is it online at the moment?
The server is down: ANCHOR TEST - local stand is offline now, with the last sighting 23 days 7 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 24 September 2026, Rust Server Score saw it for the first time.
What Rust version is ANCHOR TEST - local stand on?
You will find ANCHOR TEST - local stand on Rust network protocol 2634 and build 166652, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Resets
How frequently does ANCHOR TEST - local stand wipe its map?
ANCHOR TEST - local stand has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 23 days 7 hours have passed since this world was made.
What should you expect from wipe day on ANCHOR TEST - local stand?
Across its recent wipes, the busiest moments averaged 0 players. 1 hours after the latest wipe began, the crowd hit its peak.
Player numbers
Where does ANCHOR TEST - local stand sit among Rust servers?
In the top 71% of all ranked servers, ANCHOR TEST - local stand sits at #16,009 for player hours over the last seven days.
Is ANCHOR TEST - local stand a busy server?
ANCHOR TEST - local stand is offline at the moment; the last time it was seen was 23 days 7 hours ago.
Lists and filters
How should you read the tags on ANCHOR TEST - local stand?
The game's browser takes its cue from the tags ANCHOR TEST - local stand has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp4 (Max players): The server holds 4 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): Join only if your game runs protocol 2634; cs166652 (Build): This runs on build 166652; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded. 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 ANCHOR TEST - local stand?
These Rust Server Score lists count ANCHOR TEST - local stand among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
How is ANCHOR TEST - local stand set up, and what rules does it keep?
Nothing in the name of ANCHOR TEST - local stand states a gather rate. The group limit stays at the game's default of 8 players. survival is the mode here, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
ANCHOR TEST - local stand runs which map?
ANCHOR TEST - local stand runs a procedural map, which the game generates.
How to join
What is the way to join ANCHOR TEST - local stand?
To connect, start Rust, press F1, and type client.connect 95.105.76.2:28115. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp4,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp4
Max playersThe server holds 4 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166652
BuildThis runs on build 166652.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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 momentum (D); standing is the one to work on (F).