Offline 65.92.123.180:28015 checked 22d ago
Dev Environment - Bot Testing
Connect
srv = rust.server("65.92.123.180: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 65% 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.180: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 · 151 on average | 59/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 131/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 86/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 28/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 | 9/1000 |
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 #14,617 on player hours, in the top 65% 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 15 hours ago.
Server data
Which Rust version is Dev Environment - Bot Testing on?
The build is Rust network protocol 2634 and build 166652 on Windows, run by Dev Environment - Bot Testing. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Dev Environment - Bot Testing, and is it up?
The latest sample has Dev Environment - Bot Testing offline, with a last sighting 22 days 15 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 6 October 2026.
In which location is Dev Environment - Bot Testing hosted?
No region is published by Dev Environment - Bot Testing. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 65.92.123.180:28015 is its address.
Settings and map
Which rules apply on Dev Environment - Bot Testing, and what settings?
No gather rate appears in the name: Dev Environment - Bot Testing. No custom cap; the default of 8 players per group stands. 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. Oxide plugins run on it. Anti-cheat status: VAC off.
Which map has Dev Environment - Bot Testing selected?
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. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 24 days ago.
Tags and filters
Where does Dev Environment - Bot Testing appear among Rust Data lists and filters?
These Rust Data lists include Dev Environment - Bot Testing: 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?
These tags are published by Dev Environment - Bot Testing and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166652 (Build): Build number: 166652; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way to join Dev Environment - Bot Testing?
Enter client.connect 65.92.123.180:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.