Dev Environment - Bot Testing
Offline 143.105.195.137: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 62% 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?
The last seven days of player hours place Dev Environment - Bot Testing at #13,747, within the top 62% of all ranked servers.
How busy is Dev Environment - Bot Testing?
At this count Dev Environment - Bot Testing is offline, with its last sighting 22 days 18 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): You can join up to 10 slots; ts8 (Group limit): 8 per team is the default limit; v2634 (Protocol): To join, your game must match protocol 2634; 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): A plugin framework, Oxide (uMod), is in use; ^z (Modded): Plugins or settings change the game; it is listed under Modded. The tags also carry the current player count, the queue and when the world was made; you will find them at the top of this page.
Which Rust Population lists and filters include Dev Environment - Bot Testing?
These Rust Population lists include Dev Environment - Bot Testing: 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?
Its rhythm cannot be told yet: too few of Dev Environment - Bot Testing's wipes are on record. The next monthly force wipe is on Thursday 5 November at 19:00 UTC; all Rust servers wipe then, this one too. Counted from 24 days 19 hours ago, that is how long the current world has stood.
Map and rules
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?
No gather rate appears in the name of Dev Environment - Bot Testing. The group limit is 8 players, which is the default. 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. VAC, Valve's anti-cheat, is not running.
Server details
Which version of Rust does Dev Environment - Bot Testing run?
On Windows, Dev Environment - Bot Testing runs Rust network protocol 2634 and build 166652. 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?
We last saw Dev Environment - Bot Testing 22 days 18 hours ago, and it is offline now. Over the last 7 full days, 0 of 168 hours were online, or 0%. On 6 October 2026, Rust Population saw it for the first time.
Where is Dev Environment - Bot Testing located?
Nothing published by Dev Environment - Bot Testing states a region. What Rust Population shows is where a server says it is; where the machine actually stands is not looked up. You will find it at 143.105.195.137:28015.
Getting in
How do I join Dev Environment - Bot Testing?
Open the console with F1 in Rust and enter client.connect 143.105.195.137:28015. Joining from this page with Launch Rust works too, opening Rust through Steam and connecting you.