Offline 86.49.84.105:28015 checked 14d ago
Local Rust Bot Test
Connect
srv = rust.server("86.49.84.105:28017")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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
srv.rank.plot(invert=True) # 1 is best
Top 60% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.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
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())
Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 86.49.84.105:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 10 Oct 2026, 22:31 UTC
- hostname
- –
- first seen
- 13 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | NA · no group limit · biweekly · 250 on average | 283/2000 |
| 1 | [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | EU · no group limit · biweekly · 241 on average | 99/2000 |
| 2 | Chrayntopia ♡ ︎PvE | RP | PvP | NA · groups of 8+ · biweekly · 104 on average | 147/200 |
| 3 | 【炮炮PVE启蒙】纯净|特色|突袭|技能 | EA · groups of 16+ · biweekly · 60 on average | 35/200 |
| 4 | [PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendl | groups of 30+ · monthly · 53 on average | 55/300 |
| 5 | TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 | EU · groups of 30+ · biweekly · 51 on average | 7/100 |
Quick answers
From the figures on this page.
Population
What position does Local Rust Bot Test take in the server rankings?
Player hours over seven days put Local Rust Bot Test at #12,988, in the top 60% of the ranked set.
How many players does Local Rust Bot Test hold at once?
Local Rust Bot Test returns no live count at this refresh, having last been seen 14 days 16 hours ago.
About the server
What is the Rust version on Local Rust Bot Test?
Rust network protocol 2634 and build 167398 on Windows is what Local Rust Bot Test runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Local Rust Bot Test, and is it online now?
Local Rust Bot Test is offline at this refresh; the last response came 14 days 16 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 13 October 2026.
Where does Local Rust Bot Test sit?
For Local Rust Bot Test, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 86.49.84.105:28015 is its address.
Settings and map
Which settings and rules does Local Rust Bot Test run?
The name Local Rust Bot Test carries no gather rate. No custom cap; the default of 8 players per group stands. pve is the game mode here, and no combat between players. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. The VAC field reads off.
Which map has Local Rust Bot Test selected?
A procedural map runs on Local Rust Bot Test, generated by the game.
Wipe data
When does Local Rust Bot Test wipe, and on what schedule?
Too few wipes are on record for Local Rust Bot Test to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 18 days 4 hours ago, and that is the one in play.
Tags, lists
Which Rust Data filters and lists contain Local Rust Bot Test?
The Rust Data lists that Local Rust Bot Test fits are: Modded Rust servers and Rust PvE servers. Under these filters on the server list, it is listed: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server 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): Rust survival in its standard form; mp1 (Max players): The server lists 1 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167398 (Build): Build number: 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^p (PvE): PvE: the world is the threat, not other players; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way to join Local Rust Bot Test?
The manual route: launch Rust, F1, then client.connect 86.49.84.105:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.