Working its way up from the back of the class: #13,933 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
51/ 100
D
Moving up: up 394 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.
No daily history yet.
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 64% 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
You'll find no region listed by LOCAL TEST SERVER. Rust Server Score takes the server's word for its location and does not trace the hardware. 84.40.239.96:28055 is the address to use.
How reliable is LOCAL TEST SERVER, and is it up?
You cannot join now: LOCAL TEST SERVER is offline, last seen 34 days 6 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 23 September 2026.
Which Rust version is LOCAL TEST SERVER running?
Rust network protocol 2633 and build 165367 on Windows is what LOCAL TEST SERVER runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
On what schedule does LOCAL TEST SERVER reset?
There are too few wipes on record for LOCAL TEST SERVER to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 34 days 6 hours.
Player count
Where does LOCAL TEST SERVER sit among Rust servers?
Over the last seven days, LOCAL TEST SERVER has #13,933 for player hours, in the top 64% of all ranked servers.
What does the population on LOCAL TEST SERVER look like?
LOCAL TEST SERVER is offline at the moment; the last time it was seen was 34 days 6 hours ago.
Tags
How should you read the tags on LOCAL TEST SERVER?
The game's browser takes its cue from the tags LOCAL TEST SERVER has set: gmrust (Game mode): Rust survival, played by the standard rules; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): Join only if your game runs protocol 2633; cs165367 (Build): The game build is 165367; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): Plugin framework: Carbon. 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 Rust Server Score filters and lists feature LOCAL TEST SERVER?
Rust Server Score lists that include LOCAL TEST SERVER: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Server rules
What settings and rules apply on LOCAL TEST SERVER?
Nothing in the name of LOCAL TEST SERVER states a gather rate. With no change from the game default, groups take up to 8 players. It runs survival, gather, build and raid, as in 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 Carbon. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map LOCAL TEST SERVER uses?
LOCAL TEST SERVER runs a procedural map, which the game generates.
Connecting
How should you connect to LOCAL TEST SERVER?
Enter client.connect 84.40.239.96:28055 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 asmp10,ptrak,$r?,v2633,gmrust,cs165367,ts8,^z,^y
Game
gmrust
Game modeRust survival, played by the standard rules.
mp10
Max playersThe server holds 10 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs165367
BuildThe game build is 165367.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
^y
CarbonPlugin framework: Carbon.
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).