Station XX-13747 · no signal
Dev Environment - Bot Testing
Offline 143.105.195.137:28015 checked 22d ago
- Players now
- 1/ 10
- 10% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #13,747
- top 62%
- 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 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
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 pageRules and settings
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. The group limit is 8 players, the game's default. In survival mode, gather, build and raid in the standard game. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. Oxide is the plugin framework it runs. Anti-cheat is off: VAC, from Valve.
Population
How many players are recorded on Dev Environment - Bot Testing right now?
Dev Environment - Bot Testing is not responding at this moment and is offline, last seen 22 days 12 hours ago.
How does Dev Environment - Bot Testing rank against other Rust servers?
On player hours for the past week, Dev Environment - Bot Testing sits at #13,747, which puts it inside the top 62% of every ranked server.
Server details
How reliably does Dev Environment - Bot Testing stay online?
As recorded now, Dev Environment - Bot Testing is not reachable, the last contact having been 22 days 12 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. 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. The address it publishes is 143.105.195.137:28015.
Which Rust version is Dev Environment - Bot Testing running?
On Windows, Dev Environment - Bot Testing runs Rust network protocol 2634 and build 166652. The protocol must match for you to join, and Steam takes care of updating it.
Wipe pattern
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 14 hours.
Server 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): 10 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs166652 (Build): The game build is 166652; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does Dev Environment - Bot Testing appear?
You will find Dev Environment - Bot Testing on the following Rust Server Trends lists: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How to join
How do you connect to Dev Environment - Bot Testing?
To join, enter client.connect 143.105.195.137: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.