Dev Environment - Bot Testing
Offline 143.105.195.137:28015 checked 22d ago
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.
Rules and settings
Where can you read the rules and settings that apply on Dev Environment - Bot Testing?
You will find no gather rate in the name of Dev Environment - Bot Testing. The default group limit of 8 players applies. Filed under survival, building, gathering and raiding in the standard game. PvP and raiding are allowed. Plugins or settings change the game; it is listed under Modded in the server browser. Plugins in use: Oxide. VAC is off: Valve's anti-cheat is disabled.
Which map is in use on Dev Environment - Bot Testing?
A procedural map, generated by the game, is what Dev Environment - Bot Testing runs.
Lists and filters
Which lists and filters on Rust Server Index is Dev Environment - Bot Testing filed under?
Filed under these Rust Server Index lists is Dev Environment - Bot Testing: Modded Rust servers, filed by play style. It appears under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
What is meant by the tags on Dev Environment - Bot Testing?
Filed under these tags, as published by Dev Environment - Bot Testing and read by the game's server browser: gmrust (Game mode): Rust survival, as standard; mp10 (Max players): 10 slots are available; ts8 (Group limit): Teams cap at 8, the default setting; v2634 (Protocol): Joining needs you on game protocol 2634; cs166652 (Build): The game build here is 166652; ptrak (Networking): Networking runs on RakNet, the game's default layer; $r? (Region code): The region code field is left empty; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): This one is Modded, since plugins or settings change how it plays. The top of this page shows three items from the tags: players at present, queue and world creation time.
Wipes and resets
When does Dev Environment - Bot Testing wipe?
The record holds too few of Dev Environment - Bot Testing's wipes to tell its rhythm. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. Its present world dates from 24 days 15 hours.
Player counts
What position does Dev Environment - Bot Testing hold among Rust servers?
Filed under rankings: #13,747 for Dev Environment - Bot Testing on seven-day player hours, top 62% overall.
What does the player count on Dev Environment - Bot Testing look like?
At present Dev Environment - Bot Testing is offline; its last sighting was 22 days 13 hours ago.
Server facts
What version does Dev Environment - Bot Testing use?
Rust network protocol 2634 and build 166652, on Windows, is what Dev Environment - Bot Testing runs. To join you need the same protocol; Steam handles the update.
How reliable is Dev Environment - Bot Testing, and is it online now?
The server is down at this moment; the last sighting of Dev Environment - Bot Testing was 22 days 13 hours ago. Of the last 7 full days, 0 of 168 hours were up, 0% of the time. It was first recorded by Rust Server Index on 6 October 2026.
Which region is Dev Environment - Bot Testing in?
No region is published by Dev Environment - Bot Testing. No lookup of the machine's position is made by Rust Server Index; it shows where the server says it is. You will reach it at 143.105.195.137:28015.
Connecting
What steps lead onto Dev Environment - Bot Testing?
Two ways in. Type client.connect 143.105.195.137:28015 into the Rust console after pressing F1, or use Launch Rust and join on this page, which opens Rust through Steam and connects you.
Server tags
What each one means.
Published as mp10,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z
Game
gmrust
mp10
ts8
v2634
cs166652
ptrak
$r?
Mods and access
^o
^z
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.