On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 150% full
7-day average1peak 1
Rank#6,178top 28%
Last wipe21d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
6/ 100
F
A quiet classroom so far: 1 of 15 on average. Plenty of space to grow.
Standingrank on player hours
72/ 100
B−
Holds a respectable place: #6,178 on player hours.
Uptimehours on the list, last 48
40/ 100
F
Attendance needs work: on the list only 19 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 123 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
59/ 100
C−
Moving up: up 1,172 places this week.
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
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeak
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 17 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 28% 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
No region is published for Local Test Server. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 2.135.124.80:28015.
How dependable is Local Test Server, and is it online at the moment?
You cannot join now: Local Test Server is offline, last seen 4 hours ago. About 17 hours ago, it restarted, based on the uptime it reports. For the last 7 full days, it was up 19 of 168 hours, or 11% of the time. It was first seen by Rust Server Score on 17 October 2026.
How well does Local Test Server run?
It never fell below 94 server fps in the last 48 hours, averaging 123. Buildings, deployables and everything else in the world added up to as many as 80,191 entities. Memory use reached up to 2,330 MB. When fps is low and entities climb, that is lag to players.
Which Rust version is Local Test Server running?
The server Local Test Server is on Rust network protocol 2635 and build 168909 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does Local Test Server wipe its map?
Local Test Server has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 21 days 21 hours.
Player count
Where does Local Test Server sit among Rust servers?
Over the last seven days, Local Test Server has #6,178 for player hours, in the top 28% of all ranked servers.
Is Local Test Server a busy server?
The last sighting of Local Test Server was 4 hours ago, and it is offline right now. The seven-day average is 1 players, with a peak of 1. The highest average in the last 48 hours came at 13:00 UTC, with 1 players.
Tags and filters
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): This one runs plain Rust survival, with nothing altered; mp15 (Max players): Its slot count is 15; 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): 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; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings; you will find it 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 Test Server?
These Rust Server Score lists count Local Test Server among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
What settings and rules apply on Local Test Server?
Nothing in the name of Local Test Server states a gather rate. The group limit stays at the game's default of 8 players. It runs survival, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map Local Test Server uses?
Local Test Server runs a game-generated procedural map at size 3,750, seed 12345. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
What is the way to join Local Test Server?
Enter client.connect 2.135.124.80: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 asmp15,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp15
Max playersIts slot count is 15.
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
BuildThe game build is 168909.
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
ModdedThe game is changed by plugins or settings; you will find it 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 fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).