Station XX-15945 · no signal
Dev Environment - Bot Testing
Offline 65.92.123.62:28015 checked 23d ago
- Players now
- 0/ 10
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,945
- top 71%
- 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
- 0of 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 71% 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 pageServer 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?
No gather rate appears in the name of Dev Environment - Bot Testing. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. The plugins run on Oxide. Anti-cheat is off: VAC, from Valve.
Live population
What is the current population on Dev Environment - Bot Testing?
A reading taken now finds Dev Environment - Bot Testing offline; the most recent activity was 23 days 6 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 #15,945, in the top 71% of all ranked servers.
Operator and location
How reliably does Dev Environment - Bot Testing stay online?
Dev Environment - Bot Testing is down at the moment; the last recorded contact was 23 days 6 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 5 October 2026 is when Rust Server Trends first recorded it.
Where in the world is Dev Environment - Bot Testing hosted?
No region is published by 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 65.92.123.62:28015.
What build of Rust does Dev Environment - Bot Testing use?
Dev Environment - Bot Testing is running Rust network protocol 2634 and build 166652 on a machine with Windows. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe schedule
On what timetable does Dev Environment - Bot Testing run its wipes?
On record so far are too few of Dev Environment - Bot Testing's wipes to tell its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 24 days 6 hours.
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): You'll find standard Rust survival here; mp10 (Max players): The server has 10 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166652 (Build): Game build: 166652; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. You will find its current players, queue and world creation time among the tags, displayed 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
How do you connect to Dev Environment - Bot Testing?
You can connect by pressing F1 in Rust and typing client.connect 65.92.123.62:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects 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.