Working its way up from the back of the class: #13,648 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
39/ 100
F
Slipped a little: down 3,018 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to 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 62% 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 Rust Bot Test. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 85.193.1.200:28015.
How dependable is Local Rust Bot Test, and is it online at the moment?
You cannot join now: Local Rust Bot Test is offline, last seen 17 days 18 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 10 October 2026.
What Rust version is Local Rust Bot Test on?
Rust network protocol 2634 and build 167398 on Windows is what Local Rust Bot Test runs. Steam updates your game for you, but you need the same protocol to join.
Resets
When does Local Rust Bot Test wipe, and how often?
The record holds too few of Local Rust Bot Test's wipes to tell 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 17 days 22 hours.
Player numbers
Where does Local Rust Bot Test sit among Rust servers?
Over the last seven days, Local Rust Bot Test has #13,648 for player hours, in the top 62% of all ranked servers.
Is Local Rust Bot Test a busy server?
It has been 17 days 18 hours since Local Rust Bot Test was last seen, and it is offline right now.
Lists 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): Survival in the standard Rust style; mp1 (Max players): 1 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): Join only if your game runs protocol 2634; cs167398 (Build): This runs on build 167398; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^p (PvE): The danger comes from the world, not from other players; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^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. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show Local Rust Bot Test?
Rust Server Score lists that include Local Rust Bot Test: 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
How is Local Rust Bot Test set up, and what rules does it keep?
Nothing in the name of Local Rust Bot Test states a gather rate. The group limit stays at the game's default of 8 players. It runs pve, no PvP between players. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. You are not covered by VAC, Valve's anti-cheat.
Can you tell me which map Local Rust Bot Test uses?
Local Rust Bot Test runs a procedural map, which the game generates.
How to join
How do you get onto Local Rust Bot Test?
Enter client.connect 85.193.1.200: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 asmp1,ptrak,$r?,v2634,^p,gmrust,cs167398,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp1
Max players1 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167398
BuildThis runs on build 167398.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Gameplay
^p
PvEThe danger comes from the world, not from other players.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^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 term to build on. Even marks across the subjects, from F to F.