On the class lists: C+ (66), with population over 48 hours and no performance mark.
Players now1/ 1100% full
7-day average1peak 1
Rank#8,601top 39%
Last wipe17d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
89/ 100
A−
A full classroom nearly all week: 1 of 1 on average.
Standingrank on player hours
61/ 100
C
Working its way up from the back of the class: #8,601 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
70/ 100
B−
Climbing fast: up 3,355 places this week.
A steady term.
Strongest in population (A−); standing is the one to work on (C).
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.
AveragePeak
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 39% 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 reports the location a server gives; it does not check where the machine actually is. You can connect at 77.240.177.48:28015.
Is Local Rust Bot Test up, and how steady is its uptime?
You cannot join now: Local Rust Bot Test is offline, last seen 6 days 11 hours ago. It was up 3% of the time over the last 6 full days, 5 of 144 hours. The first sighting by Rust Server Score was on 21 October 2026.
Which Rust version is Local Rust Bot Test running?
You will find Local Rust Bot Test on Rust network protocol 2634 and build 167398, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does Local Rust Bot Test wipe its map?
Local Rust Bot Test 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. The world it runs now was created 17 days 17 hours.
Player count
What position does Local Rust Bot Test hold in the rankings?
In the top 39% of all ranked servers, Local Rust Bot Test sits at #8,601 for player hours over the last seven days.
Is Local Rust Bot Test a busy server?
It has been 6 days 11 hours since Local Rust Bot Test was last seen, and it is offline right now. Averaging 1 players over seven days, it peaked at 1.
Lists and filters
How should you read the tags on Local Rust Bot Test?
The game's browser takes its cue from the tags Local Rust Bot Test has set: gmrust (Game mode): Survival in the standard Rust style; mp1 (Max players): Its slot count is 1; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167398 (Build): Build number: 167398; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^p (PvE): Players do not fight one another here; the world is the danger; ^o (Oxide): Plugin framework: Oxide (uMod); ^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.
Where does Local Rust Bot Test appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Local Rust Bot Test: Modded Rust servers, graded and Rust PvE servers, graded. You can find it under these server-list filters: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
Which rules does Local Rust Bot Test enforce, and what are its settings?
You will find no gather rate in the name of Local Rust Bot Test. The default of 8 players applies as the group cap. It runs pve, no PvP between players. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. You are not covered by VAC, Valve's anti-cheat.
Local Rust Bot Test runs which map?
Local Rust Bot Test runs a procedural map, which the game generates.
How to join
What is the way to join Local Rust Bot Test?
To connect, start Rust, press F1, and type client.connect 77.240.177.48: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 modeSurvival in the standard Rust style.
mp1
Max playersIts slot count is 1.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167398
BuildBuild number: 167398.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^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 steady term. Strongest in population (A−); standing is the one to work on (C).