Local Rust Bot Test
Key statistics
the figures behind the quote- Players now
- 1/ 1 100% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 1 peak 1
- Rank
- #10,606 top 48%
- Rank · 7d ago
- – not ranked a week ago
- Last wipe
- 3d ago no schedule published
- Next wipe
- – no wipe seen yet
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 4 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 10 Oct 2026 no hostname published
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
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 wipes| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoEU · no group limit · biweekly · 205 on average | 188/2000 | ▼−38−16.8% | |
| 2 | [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoNA · no group limit · biweekly · 201 on average | 72/2000 | ▼−64−47.1% | |
| 3 | 1[PvE]Тульский|Русский|Classic+ИвентыEU · groups of 8+ · monthly · 75 on average | 81/200 | ▲+5+6.6% | |
| 4 | 桃乐丝 PVE - 经济 | 养殖 | 技能 | 钓鱼 | 传奇装EA · groups of 8+ · monthly · 74 on average | 26/100 | ▼−54−67.5% | |
| 5 | [US] RustEZ Scourge PvE | Zombies | No Raiding | No KillingNA · groups of 8+ · monthly · 64 on average | 45/200 | ▲+3+7.6% | |
| 6 | Japan Tokyo - Vanilla PvE|JP|BeginnerEA · groups of 16+ · 63 on average | 93/100 | ▲+2+1.6% |
Quick answers
from the figures on this pageRules & Settings
What settings and rules are in place on Local Rust Bot Test?
No gather rate appears in the name of Local Rust Bot Test. Up to 8 players per group, which is the game's default. pve is the mode, player-versus-player combat is absent. Modded is its category in the server browser; plugins or settings modify the game. Plugin count: Oxide. VAC, Valve's anti-cheat, is disabled.
Which map is played on Local Rust Bot Test?
Local Rust Bot Test uses a procedural map, which the game generates.
Population
Where does Local Rust Bot Test sit in the rankings?
For the last seven days, Local Rust Bot Test holds rank #10,606 on player hours, in the top 48% of all ranked servers.
How full is Local Rust Bot Test?
At present, Local Rust Bot Test is offline; the last sighting was 3 days 10 hours ago. The mean over the last seven days is 1 players, reaching 1 at its highest.
Wipe Cycle
How often does Local Rust Bot Test wipe?
The record holds too few of Local Rust Bot Test's wipes to establish its rhythm. The monthly force wipe takes every Rust server. Next: Thursday 5 November at 19:00 UTC. Its world now is 3 days 14 hours old.
Server Overview
What is the server location for Local Rust Bot Test?
There is no region published for Local Rust Bot Test. The location shown by Rust Analytics is the one a server states; it does not verify the machine's position. You can reach it at 85.193.1.200:28015.
Local Rust Bot Test runs which version of Rust?
The version in use at Local Rust Bot Test: Rust network protocol 2634 and build 167398, on Windows. The protocol has to match for you to join, and Steam applies that update.
How reliable is Local Rust Bot Test and is it currently online?
Offline at this moment: Local Rust Bot Test. Last seen 3 days 10 hours ago. The last 3 full days give 4% uptime, 3 hours on out of 72. 10 October 2026 is when Rust Analytics first saw it.
Tags and Rankings
How should you interpret the tags on Local Rust Bot Test?
These tags are published by Local Rust Bot Test and read by the game's server browser: gmrust (Game mode): Survival in the standard Rust format; mp1 (Max players): Slot count: 1; ts8 (Group limit): At the game default, teams hold up to 8; v2634 (Protocol): To join, your game needs protocol 2634; cs167398 (Build): It runs build 167398; ptrak (Networking): The standard network layer, RakNet; $r? (Region code): The region code is absent; ^p (PvE): The world is the danger here, not other players; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): The Modded listing applies: plugins or settings change play. The tags also carry its current players, queue and world creation time; this page shows them at the top.
Where does Local Rust Bot Test show up in Rust Analytics lists and filters?
On Rust Analytics, Local Rust Bot Test matches these lists: Modded Rust servers and Best Rust PvE servers. It appears under these filters 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 to Join
What is the process to join Local Rust Bot Test?
The console route: start Rust, press F1, enter client.connect 85.193.1.200:28015. The page's Launch Rust button opens Rust through Steam and connects you instead.
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.