Dev Environment - Bot Testing
Offline 65.92.123.62:28015 checked 22d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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
daily · 1 is bestTop 71% 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
newest first| 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 43/500
- 135/100
- 48/225
- 17/700
- 1/200
- 4/1000
Quick answers
from the figures on this pageWipe schedule
What wipe timing does Dev Environment - Bot Testing follow?
Its rhythm cannot be told from the wipes of Dev Environment - Bot Testing on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 23 days 23 hours ago.
Tags
How should you read the tags on Dev Environment - Bot Testing?
These are the tags Dev Environment - Bot Testing publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166652 (Build): Game build reading: 166652; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show Dev Environment - Bot Testing?
These Rust Metrics lists carry Dev Environment - Bot Testing: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Occupancy
Where does Dev Environment - Bot Testing sit in the rankings?
Player hours over seven days put Dev Environment - Bot Testing at #15,945, in the top 71% of all ranked servers.
How full does Dev Environment - Bot Testing get?
Reading for Dev Environment - Bot Testing: offline at this moment; last seen 22 days 23 hours ago.
Server
What location is Dev Environment - Bot Testing hosted in?
Reading: location. Dev Environment - Bot Testing gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 65.92.123.62:28015.
What Rust version is Dev Environment - Bot Testing on?
Reading: Dev Environment - Bot Testing, Rust network protocol 2634 and build 166652, Windows. To get in, your game needs the same protocol; Steam applies the update.
What is the uptime on Dev Environment - Bot Testing, and is it online?
Check: connection. Dev Environment - Bot Testing is offline at this moment. Last contact was 22 days 23 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 5 October 2026.
Rules and settings
What rules does Dev Environment - Bot Testing enforce, and what are its settings?
No gather rate appears in the name: Dev Environment - Bot Testing. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Oxide of them. VAC is off. That is Valve's anti-cheat.
What map is Dev Environment - Bot Testing on?
The game generates a procedural map for Dev Environment - Bot Testing.
How to join
How do you connect to Dev Environment - Bot Testing?
Check: join. Open Rust, press F1, then enter client.connect 65.92.123.62:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.