Station XX-14617 · no signal
Dev Environment - Bot Testing
Offline 65.92.123.180:28015 checked 22d ago
- Players now
- 1/ 10
- 10% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #14,617
- top 65%
- Last wipe
- 24d ago
- no schedule published
- Next wipe
- –
- no wipe seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 10 slots
- Motion · 24 h
- M –not enough readings
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
daily · 1 is bestTop 65% 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
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageMap and rules
Which map is running on Dev Environment - Bot Testing?
A procedural map runs on Dev Environment - Bot Testing, generated by the game.
Which settings and rules apply on Dev Environment - Bot Testing?
The name of Dev Environment - Bot Testing gives no gather rate. Groups hold up to 8 players, which is the default for the game. survival is the game mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Oxide. The server has VAC off, Valve's anti-cheat.
Population
What is the current population on Dev Environment - Bot Testing?
Dev Environment - Bot Testing is not responding at this moment and is offline, last seen 22 days 21 hours ago.
How does Dev Environment - Bot Testing rank against other Rust servers?
The last seven days of player hours place Dev Environment - Bot Testing at #14,617, in the top 65% of all ranked servers.
Server details
How reliably does Dev Environment - Bot Testing stay online?
Dev Environment - Bot Testing is down at the moment; the last recorded contact was 22 days 21 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 6 October 2026.
Where in the world is Dev Environment - Bot Testing hosted?
Nothing about a region comes from Dev Environment - Bot Testing. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 65.92.123.180:28015 is the address it uses.
Which Rust version is Dev Environment - Bot Testing running?
On Windows, Dev Environment - Bot Testing runs Rust network protocol 2634 and build 166652. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe schedule
How often does Dev Environment - Bot Testing wipe, and on which days?
The rhythm of Dev Environment - Bot Testing cannot yet be told: too few of its wipes are on record. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 24 days 7 hours.
Tags
What do the server tags on Dev Environment - Bot Testing mean?
Tags published by Dev Environment - Bot Testing and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp10 (Max players): The server has 10 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166652 (Build): It runs game build 166652; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does Dev Environment - Bot Testing appear?
These Rust Server Trends lists include Dev Environment - Bot Testing: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Join the server
What steps get you onto Dev Environment - Bot Testing?
To join, enter client.connect 65.92.123.180:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.