Station XX-13648 · no signal
Local Rust Bot Test
Offline 85.193.1.200:28015 checked 17d ago
- Players now
- 1/ 1
- 100% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #13,648
- top 62%
- Last wipe
- 17d ago
- no schedule published
- Next wipe
- –
- no wipe seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 1 slots
- Motion · 24 h
- M –not enough readings
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 62% 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 | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 and settings
Which map is running on Local Rust Bot Test?
A procedural map runs on Local Rust Bot Test, generated by the game.
Which settings and rules apply on Local Rust Bot Test?
You will find no gather rate in the name of Local Rust Bot Test. At the game's default, groups can have up to 8 players. pve is the game mode, no combat against other players. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Oxide. The server has VAC off, Valve's anti-cheat.
Player counts
What is the current population on Local Rust Bot Test?
A reading taken now finds Local Rust Bot Test offline; the most recent activity was 17 days 2 hours ago.
How does Local Rust Bot Test rank against other Rust servers?
Over the last seven days, Local Rust Bot Test recorded enough player hours to reach #13,648 worldwide, placing it in the top 62% of all ranked servers.
Operator and location
How reliably does Local Rust Bot Test stay online?
Local Rust Bot Test is down at the moment; the last recorded contact was 17 days 2 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 10 October 2026 it was recorded for the first time by Rust Server Trends.
Which region does Local Rust Bot Test run from?
Nothing about a region comes from Local Rust Bot Test. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 85.193.1.200:28015.
What build of Rust does Local Rust Bot Test use?
Local Rust Bot Test is running Rust network protocol 2634 and build 167398 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
How often does Local Rust Bot Test wipe, and on which days?
Too few wipes of Local Rust Bot Test are on record yet to show its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 17 days 6 hours is how long the current world has been running.
Lists and tags
What do the server tags on Local Rust Bot Test mean?
These are the tags Local Rust Bot Test publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp1 (Max players): 1 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167398 (Build): Game build: 167398; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^p (PvE): The danger comes from the world, not from other players; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does Local Rust Bot Test appear?
The Rust Server Trends lists that take in Local Rust Bot Test are: Modded Rust servers, tracked live and Rust PvE servers. On the server list, the filters it matches are: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.
How to join
How do you connect to Local Rust Bot Test?
To join, enter client.connect 85.193.1.200:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.