Offline 65.92.123.62:28015 checked 22d ago
Dev Environment - Bot Testing
Connect
srv = rust.server("65.92.123.62: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 71% 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
- 65.92.123.62:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 5 Oct 2026, 05:39 UTC
- hostname
- –
- first seen
- 5 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 · 154 on average | 28/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 129/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 36/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 12/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 3/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 1/1000 |
Quick answers
From the figures on this page.
Population data
What position does Dev Environment - Bot Testing take in the server rankings?
Over the last seven days Dev Environment - Bot Testing sits at #15,945 on player hours, in the top 71% of ranked servers.
How many players does Dev Environment - Bot Testing hold at once?
Offline now for Dev Environment - Bot Testing, with the last sample 22 days 22 hours ago.
Server facts
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 22 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 5 October 2026.
In which location is Dev Environment - Bot Testing hosted?
There is no region published for Dev Environment - Bot Testing. Rust Data does not look up where the machine stands; it shows where a server says it is. 65.92.123.62:28015 is its address.
Settings and map
What rules and settings are recorded for Dev Environment - Bot Testing?
No gather rate appears in the name: Dev Environment - Bot Testing. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the usual game, with gathering, building and raiding. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. Anti-cheat status: VAC off.
Which map has Dev Environment - Bot Testing loaded?
A procedural map runs on Dev Environment - Bot Testing, generated by the game.
Wipes and dates
When does Dev Environment - Bot Testing wipe, and on what schedule?
The record for Dev Environment - Bot Testing holds too few wipes to show a rhythm. 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 23 days 22 hours ago, and that is the one in play.
Tags, lists
Which Rust Data filters and lists contain Dev Environment - Bot Testing?
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.
Which meanings do the tags on Dev Environment - Bot Testing hold?
Read by the game's server browser, the tags Dev Environment - Bot Testing publishes are: 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): To join, your game must run protocol 2634; cs166652 (Build): The server runs build 166652; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^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.
How to join
What is the way to join Dev Environment - Bot Testing?
In Rust, F1 opens the console: type client.connect 65.92.123.62:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.