Dev Environment - Bot Testing
Offline 143.105.195.137:28015 checked 22d 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 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.
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. These filters bring it up 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?
The game's server browser picks up these tags from Dev Environment - Bot Testing: gmrust (Game mode): Plain vanilla Rust survival, nothing bolted on; mp10 (Max players): It has 10 slots; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): You need the same game version to get in: protocol 2634; cs166652 (Build): Game build: 166652; ptrak (Networking): RakNet is the network layer, the game's standard one; $r? (Region code): Region code left blank; ^o (Oxide): Oxide (uMod), a plugin framework, is what it runs; ^z (Modded): The game is changed by plugins or settings, hence the Modded listing. Current players, queue and world age are in the tags too, displayed 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 #13,747, within the top 62% of ranked servers.
How many players are on Dev Environment - Bot Testing right now?
Dev Environment - Bot Testing went quiet 22 days 22 hours ago and is offline at the moment.
Server details
Is Dev Environment - Bot Testing online, and how reliable is it?
Down at the moment: Dev Environment - Bot Testing was last seen 22 days 22 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours in total. The first time Rust Pop Watch saw it was 6 October 2026.
Where is Dev Environment - Bot Testing located?
No region is published by Dev Environment - Bot Testing. Rust Pop Watch does not look up where the machine stands; it shows where a server says it is. You'll find it at 143.105.195.137: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. To join, your game must be on the same protocol; Steam handles the update.
Wipe times
What is the wipe schedule on Dev Environment - Bot Testing?
Too few wipes are on record for Dev Environment - Bot Testing to reveal its rhythm. The monthly force wipe takes every Rust server down for a new world, and the next one lands on Thursday 5 November at 19:00 UTC. The world it is running now dates from 24 days 23 hours.
The 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?
Nothing in the name tells you the gather rate on Dev Environment - Bot Testing. Groups go up to 8 players, which is the default. survival is the game mode, the usual game of gathering, building and raiding. Raids and PvP are both on the table. 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.
How to join
How do I join Dev Environment - Bot Testing?
The console method: start Rust, press F1, and type client.connect 143.105.195.137:28015. Launch Rust on this page is another way, opening Rust via Steam and connecting.