Offline 213.175.37.210:28015 checked 7d ago
Local Rust Bot Test
Connect
srv = rust.server("213.175.37.210: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 59% 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
- 213.175.37.210:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 10 Oct 2026, 22:31 UTC
- hostname
- –
- first seen
- 22 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 · 245 on average | 155/2000 |
| 1 | [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | EU · no group limit · biweekly · 241 on average | 102/2000 |
| 2 | Chrayntopia ♡ ︎PvE | RP | PvP | NA · groups of 8+ · biweekly · 100 on average | 44/200 |
| 3 | 【炮炮PVE启蒙】纯净|特色|突袭|技能 | EA · groups of 16+ · biweekly · 59 on average | 55/200 |
| 4 | [PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendl | groups of 30+ · monthly · 53 on average | 22/300 |
| 5 | TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 | EU · groups of 30+ · biweekly · 49 on average | 27/100 |
Quick answers
From the figures on this page.
Player counts
What position does Local Rust Bot Test take in the server rankings?
Over the last seven days Local Rust Bot Test sits at #13,076 on player hours, in the top 59% of ranked servers.
How many players does Local Rust Bot Test hold at once?
Offline now for Local Rust Bot Test, with the last sample 7 days 17 hours ago.
About the server
What Rust version does Local Rust Bot Test run?
The build is Rust network protocol 2634 and build 167398 on Windows, run by Local Rust Bot Test. The protocol has to match before you can join, and Steam does the updating.
Is Local Rust Bot Test up, and what does its uptime show?
Offline now for Local Rust Bot Test, last seen 7 days 17 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 22 October 2026.
Which location does Local Rust Bot Test run from?
There is no region published for Local Rust Bot Test. Rust Data does not look up where the machine stands; it shows where a server says it is. 213.175.37.210:28015 is its address.
Rules, settings, map
Which rules apply on Local Rust Bot Test, and what settings?
You will not find a gather rate in the string Local Rust Bot Test. No custom cap; the default of 8 players per group stands. Recorded as pve, player combat is not allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. VAC is not running; Valve's anti-cheat is off.
Which map has Local Rust Bot Test loaded?
The game generates its map: procedural, on Local Rust Bot Test.
Wipe data
On what schedule does Local Rust Bot Test wipe?
A rhythm cannot be read from the wipes of Local Rust Bot Test on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 19 days 8 hours ago, and that is the one in play.
Tags, lists
Where does Local Rust Bot Test appear among Rust Data lists and filters?
These Rust Data lists include Local Rust Bot Test: 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.
How should you read the server tags on Local Rust Bot Test?
The game's server browser reads these tags from Local Rust Bot Test: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): Slot count: 1; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167398 (Build): Recorded game build: 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^p (PvE): No player-versus-player combat; the danger comes from the world; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
How can I connect to Local Rust Bot Test?
In Rust, F1 opens the console: type client.connect 213.175.37.210:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.