Dev Environment - Bot Testing
Offline 65.92.123.62:28015 checked 24d ago
Vital stats
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 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
| 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.
Quick answers
From the figures on this page.
Tags
Which Rust Pop Watch lists and filters include Dev Environment - Bot Testing?
These Rust Pop Watch lists include Dev Environment - Bot Testing: Modded Rust servers, live. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
What do the server tags on Dev Environment - Bot Testing mean?
For the server browser, Dev Environment - Bot Testing lists these tags: gmrust (Game mode): This one runs standard Rust survival, as it comes; mp10 (Max players): It has 10 slots; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): The game protocol is 2634, so your client has to match it to join; cs166652 (Build): The game build is 166652; ptrak (Networking): The network layer is RakNet, which is the game's standard; $r? (Region code): Region code left blank; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): The game is changed by plugins or settings, hence the Modded listing. You'll find players now, queue length and world creation time in the tags, printed at the top of this page.
Player counts
How does Dev Environment - Bot Testing rank against other Rust servers?
Player hours over the last week rank Dev Environment - Bot Testing at #15,945, within the top 71% of ranked servers.
How many players are on Dev Environment - Bot Testing right now?
Dev Environment - Bot Testing went quiet 24 days 2 hours ago and is offline at the moment.
About the server
Is Dev Environment - Bot Testing online, and how reliable is it?
Dev Environment - Bot Testing shows as offline, last spotted 24 days 2 hours ago. Out of 168 hours in the last 7 full days, it was online for 0, a 0% uptime. It came to Rust Pop Watch's attention on 5 October 2026.
Where is Dev Environment - Bot Testing located?
There is no region from Dev Environment - Bot Testing. It is where a server says it is that Rust Pop Watch shows; the machine's actual location is not looked up. Connect at 65.92.123.62:28015.
Which Rust version is Dev Environment - Bot Testing on?
Rust network protocol 2634 and build 166652 is the version Dev Environment - Bot Testing runs on Windows. Steam updates your game so it matches the protocol needed to join.
Wipe days
What is the wipe schedule on Dev Environment - Bot Testing?
Dev Environment - Bot Testing's rhythm stays hidden while so few of its wipes are on record. A force wipe comes round every month for all Rust servers, with the next on Thursday 5 November at 19:00 UTC. 25 days 2 hours is when the present world was made.
Rules and settings
Which map does Dev Environment - Bot Testing run?
The map on Dev Environment - Bot Testing is procedural, made by the game.
What are the rules and settings on Dev Environment - Bot Testing?
The name of Dev Environment - Bot Testing says nothing about gather rate. Eight players per group: that is the game's default. It runs survival, gather, build and raid, as standard. Players can raid and fight one another. It is a Modded listing: plugins or settings change how the game plays. Oxide plugins power it. VAC, Valve's anti-cheat, is switched off.
Join up
How do I join Dev Environment - Bot Testing?
The console method: start Rust, press F1, and type client.connect 65.92.123.62:28015. Launch Rust on this page is another way, opening Rust via Steam and connecting.