On the class lists: F (38), with population over 48 hours and no performance mark.
Players now1/ 1100% full
7-day average1peak 1
Rank#13,076top 59%
Last wipe18d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
100/ 100
A+
A full classroom nearly all week: 1 of 1 on average.
Standingrank on player hours
41/ 100
F
Working its way up from the back of the class: #13,076 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
36/ 100
F
Slipped a little: down 3,622 places this week. Nothing a good wipe can't fix.
A fair term, with more to come.
Strongest in population (A+); momentum 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 59% 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
Local Rust Bot Test leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 213.175.37.210:28015.
How dependable is Local Rust Bot Test, and is it online at the moment?
At this moment, Local Rust Bot Test is offline; the last time it was seen was 6 days 23 hours ago. For the last 6 full days, it was up 0 of 144 hours, or 0% of the time. On 22 October 2026, Rust Server Score saw it for the first time.
On what Rust version does Local Rust Bot Test sit?
Rust network protocol 2634 and build 167398 on Windows is what Local Rust Bot Test runs. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
When does Local Rust Bot Test wipe, and how often?
There are too few wipes on record for Local Rust Bot Test 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 18 days 14 hours.
Population
What position does Local Rust Bot Test hold in the rankings?
In the top 59% of all ranked servers, Local Rust Bot Test sits at #13,076 for player hours over the last seven days.
Is Local Rust Bot Test a busy server?
It has been 6 days 23 hours since Local Rust Bot Test was last seen, and it is offline right now. It peaked at 1 and averaged 1 players over the last seven days.
Tags and filters
What is meant by the tags on Local Rust Bot Test?
You'll see Local Rust Bot Test tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): Join only if your game runs protocol 2634; cs167398 (Build): The game build is 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^p (PvE): Players do not fight one another here; the world is the danger; ^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 in the browser, which picks them up from the server. 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.
Where does Local Rust Bot Test appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Local Rust Bot Test among them: Modded Rust servers, graded and Rust PvE servers, graded. These filters bring it up on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
What settings and rules apply on Local Rust Bot Test?
Nothing in the name of Local Rust Bot Test states a gather rate. The default of 8 players applies as the group cap. pve is the mode here, no PvP between players. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. You are not covered by VAC, Valve's anti-cheat.
Which map is in play on Local Rust Bot Test?
The game generates a procedural map for Local Rust Bot Test.
Connecting
What is the way to join Local Rust Bot Test?
To connect, start Rust, press F1, and type client.connect 213.175.37.210:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp1,ptrak,$r?,v2634,^p,gmrust,cs167398,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp1
Max playersThe server holds 1 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167398
BuildThe game build is 167398.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
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 population (A+); momentum is the one to work on (F).