Dev Environment - Bot Testing
Offline 65.92.123.180:28015 checked 22d ago
Measurements
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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
Top 65% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| 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.
Quick answers
Player counts
How does Dev Environment - Bot Testing rank against other Rust servers?
By player hours over the last seven days, Dev Environment - Bot Testing places at #14,617, within the top 65% of ranked servers.
How busy is Dev Environment - Bot Testing?
We have no live count for Dev Environment - Bot Testing right now. It was last seen 22 days 11 hours ago.
Tags
What do the server tags on Dev Environment - Bot Testing mean?
The game's server browser reads the tags Dev Environment - Bot Testing publishes: gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): The server has 10 slots; ts8 (Group limit): This is the game default: at most 8 per team; v2634 (Protocol): Your game needs the same version, protocol 2634, to join; cs166652 (Build): This server runs game build 166652; ptrak (Networking): The standard network layer, RakNet, is in use; $r? (Region code): No region code is set; ^o (Oxide): A plugin framework, Oxide (uMod), is in use; ^z (Modded): The game is changed by plugins or settings, so it is listed under Modded. You will see the player count, queue and world creation time at the top of this page, because the tags carry them too.
Which Rust Population lists and filters include Dev Environment - Bot Testing?
On Rust Population, Dev Environment - Bot Testing is filed under these lists: Modded Rust servers, counted. These are the filters it appears under when you browse the list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Wipe notes
What is the wipe schedule on Dev Environment - Bot Testing?
The record holds too few of Dev Environment - Bot Testing's wipes to show a rhythm. The next monthly force wipe is on Thursday 5 November at 19:00 UTC; all Rust servers wipe then, this one too. The world it runs now dates from 23 days 21 hours ago.
Map and rules
Which map does Dev Environment - Bot Testing run?
Dev Environment - Bot Testing uses a map the game generates: procedural.
What are the rules and settings on Dev Environment - Bot Testing?
Nothing in Dev Environment - Bot Testing's name says how gather works. No limit is set beyond the standard 8 players per group. This server runs survival, raid, build and gather: the standard game. Combat between players, raids included, is permitted. The server browser files it under Modded, where plugins or settings alter the game. Oxide plugins are in use here. The anti-cheat VAC from Valve is disabled.
Server details
Which version of Rust does Dev Environment - Bot Testing run?
The setup is Rust network protocol 2634 and build 166652 on Windows for Dev Environment - Bot Testing. The protocol must match for you to join, and Steam updates it for you.
Is Dev Environment - Bot Testing online, and how reliable is it?
Currently offline, Dev Environment - Bot Testing was last seen 22 days 11 hours ago. It was up 0% of the time over the last 7 full days, 0 out of 168 hours. It was first seen by Rust Population on 6 October 2026.
Where is Dev Environment - Bot Testing located?
Nothing published by Dev Environment - Bot Testing states a region. The location a server claims is what Rust Population shows, not the place where the machine stands. You will find it at 65.92.123.180:28015.
How to join
How do I join Dev Environment - Bot Testing?
Either enter client.connect 65.92.123.180:28015 in Rust's console after pressing F1, or use Launch Rust here to open Rust through Steam and be connected.