Offline85.193.1.200:28015checked 3d ago
Local Rust Bot Test
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 48% of all ranked servers. Ranked on player hours over the last seven days.
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
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageRules, map and settings
Which rules govern Local Rust Bot Test?
No gather rate appears in the name of Local Rust Bot Test. Groups are capped at 8 players, the default in the game. pve is the game mode, no combat against other players. The server browser lists it under Modded, because plugins or settings alter the game. Oxide plugins are running on it. Anti-cheat VAC from Valve is off.
What map is used on Local Rust Bot Test?
A procedural map is what Local Rust Bot Test runs, generated by the game.
Tags and filters
Where can Local Rust Bot Test be found in Rust Player Count lists and filters?
The Rust Player Count lists that Local Rust Bot Test fits are: Modded Rust servers and Rust PvE servers. 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; Last wipe: In the last week.
How should you interpret the tags on Local Rust Bot Test?
For the game's server browser, Local Rust Bot Test publishes: gmrust (Game mode): Survival as standard in Rust; mp1 (Max players): Capacity: 1 slots; ts8 (Group limit): This uses the default team cap: 8 players; v2634 (Protocol): Joining requires the same protocol: 2634; cs167398 (Build): Build number: 167398; ptrak (Networking): The network layer is RakNet, Rust's standard one; $r? (Region code): The region code field is empty; ^p (PvE): No player-versus-player combat: the environment provides the danger; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): It appears under Modded because plugins or settings modify the game. You will also find its current players, its queue and its world creation time in the tags, displayed at the top of this page.
Player count
What is the player count on Local Rust Bot Test?
Local Rust Bot Test is offline at the moment; the last time it was seen was 3 days 12 hours ago. The seven-day average is 1 players, with a peak of 1.
Where does Local Rust Bot Test sit in the rankings?
For player hours in the last seven days, Local Rust Bot Test ranks #10,602 and is in the top 48% of all ranked servers.
Server details
How reliable is Local Rust Bot Test, and is it online?
Local Rust Bot Test is down at the moment and was last seen 3 days 12 hours ago. For the last 3 full days, it was online for 3 of 72 hours, a 4% uptime. Rust Player Count recorded it for the first time on 10 October 2026.
What Rust version is used on Local Rust Bot Test?
On Windows, Local Rust Bot Test runs Rust network protocol 2634 and build 167398. The protocol has to match for you to join, but Steam updates it without any action from you.
What region does Local Rust Bot Test serve?
There is no region published by Local Rust Bot Test. Where a server says it is, that is what Rust Player Count shows; it does not check the machine's actual location. It is located at 85.193.1.200:28015.
Wipe schedule
What wipe pattern does Local Rust Bot Test follow?
With so few of Local Rust Bot Test's wipes on record, its rhythm remains unclear. The monthly force wipe hits every Rust server, and on Thursday 5 November at 19:00 UTC it comes next. The world in play was created 3 days 16 hours ago.
Join the server
How can I connect to Local Rust Bot Test?
Joining is done by opening the console (F1) and running client.connect 85.193.1.200:28015. Another way is the Launch Rust option on this page, which uses Steam to start Rust and put you in.
Server tags
what each one meansPublished as mp1,ptrak,$r?,v2634,^p,gmrust,cs167398,ts8,^o^z
Game
gmrust
mp1
ts8
v2634
cs167398
ptrak
$r?
Gameplay
^p
Mods and access
^o
^z
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.