Offline 143.105.195.137:28015 checked 22d ago
Dev Environment - Bot Testing
Connect
srv = rust.server("143.105.195.137: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 bestTop 62% 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
- 143.105.195.137:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 5 Oct 2026, 05:39 UTC
- hostname
- –
- first seen
- 6 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 | ShockRust | Blue | NoLimit | no group limit · 150 on average | 21/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 132/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 121 on average | 36/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 10/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 93 on average | 44/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 86 on average | 182/215 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does Dev Environment - Bot Testing rank?
Over the last seven days Dev Environment - Bot Testing sits at #13,747 on player hours, in the top 62% of ranked servers.
What population does Dev Environment - Bot Testing carry?
The current row shows Dev Environment - Bot Testing offline; the last response was 22 days 17 hours ago.
Server data
What Rust version does Dev Environment - Bot Testing run?
Rust network protocol 2634 and build 166652 on Windows is what Dev Environment - Bot Testing runs. Steam updates your game for you, but the protocol must match to join.
How reliable is Dev Environment - Bot Testing, and is it up?
Offline now for Dev Environment - Bot Testing, last seen 22 days 17 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 6 October 2026.
Where does Dev Environment - Bot Testing sit?
There is no region published for Dev Environment - Bot Testing. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 143.105.195.137:28015 is its address.
Map and rules
What rules and settings are recorded for Dev Environment - Bot Testing?
You will not find a gather rate in the string Dev Environment - Bot Testing. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC is not running; Valve's anti-cheat is off.
Which map has Dev Environment - Bot Testing loaded?
The game generates its map: procedural, on Dev Environment - Bot Testing.
Wipe schedule
On what schedule does Dev Environment - Bot Testing wipe?
Too few wipes are on record for Dev Environment - Bot Testing to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 24 days 19 hours ago.
Tags and filters
Where does Dev Environment - Bot Testing appear among Rust Data lists and filters?
The Rust Data lists that Dev Environment - Bot Testing fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on Dev Environment - Bot Testing?
The game's server browser reads these tags from Dev Environment - Bot Testing: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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
How can I connect to Dev Environment - Bot Testing?
The manual route: launch Rust, F1, then client.connect 143.105.195.137:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.