Dev Environment - Bot Testing
Offline 65.92.123.62:28015 checked 23d 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 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.
Quick answers
Population
How does Dev Environment - Bot Testing rank against other Rust servers?
Over the past week it ranks #15,945 for player hours, which puts Dev Environment - Bot Testing in the top 71% of all 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 23 days 9 hours ago.
Lists and 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): 8 per team is the default limit; v2634 (Protocol): Your game needs the same version, protocol 2634, to join; cs166652 (Build): This server runs game build 166652; ptrak (Networking): RakNet is the network layer here, as standard for the game; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework Oxide (uMod) runs on this server; ^z (Modded): This server appears under Modded because plugins or settings alter the game. 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?
Dev Environment - Bot Testing appears among the Rust Population lists that follow: 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?
Too few wipes are on record for Dev Environment - Bot Testing to show its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 24 days 9 hours ago the current world was made.
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 tells you nothing about gather rates: Dev Environment - Bot Testing states none. Eight players per group is the default, and it applies here. survival is what it runs, 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. You play with Valve's anti-cheat off: VAC.
About the server
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. Your game needs the same protocol to join; Steam takes care of updating it.
Is Dev Environment - Bot Testing online, and how reliable is it?
We last saw Dev Environment - Bot Testing 23 days 9 hours ago, and it is offline now. Over the last 7 full days, 0 of 168 hours were online, or 0%. It was first seen by Rust Population on 5 October 2026.
Where is Dev Environment - Bot Testing located?
A region is not published by Dev Environment - Bot Testing. The location a server claims is what Rust Population shows, not the place where the machine stands. 65.92.123.62:28015 is where it lives.
Getting in
How do I join Dev Environment - Bot Testing?
Open the console with F1 in Rust and enter client.connect 65.92.123.62:28015. Joining from this page with Launch Rust works too, opening Rust through Steam and connecting you.