Station XX-15349 · no signal
RustDev release test (local only)
Offline 38.64.18.70:28015 checked 1d ago
- Players now
- 0/ 10
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,349
- top 69%
- 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 69% 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 RustDev release test (local only)?
The map on RustDev release test (local only) is procedural, produced by the game.
Which settings and rules apply on RustDev release test (local only)?
No gather rate appears in the name of RustDev release test (local only). The group limit is 8 players, the game's default. In survival mode, the usual game of gathering, building and raiding. You can raid and fight other players here. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Oxide. The server has VAC on, Valve's anti-cheat.
Live population
How many players are recorded on RustDev release test (local only) right now?
No players are recorded on RustDev release test (local only) at this moment; it is offline, and the last sighting was 26 hours ago. Averaged across the last seven days, the population was 0 players.
How does RustDev release test (local only) rank against other Rust servers?
On player hours for the past week, RustDev release test (local only) sits at #15,349, which puts it inside the top 69% of every ranked server.
Operator and location
How reliably does RustDev release test (local only) stay online?
RustDev release test (local only) is down at the moment; the last recorded contact was 26 hours ago. It was up 0% of the time across the last 1 full day: 0 of 24 hours. Its earliest appearance in the records of Rust Server Trends dates to 27 October 2026.
Which region does RustDev release test (local only) run from?
Nothing about a region comes from RustDev release test (local only). Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 38.64.18.70:28015.
What build of Rust does RustDev release test (local only) use?
Rust network protocol 2635 and build 168909 on Windows is what RustDev release test (local only) runs. 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 RustDev release test (local only) run its wipes?
The rhythm of RustDev release test (local only) 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 4 hours.
Server tags
What do the server tags on RustDev release test (local only) mean?
Tags published by RustDev release test (local only) and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp10 (Max players): 10 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): Game build: 168909; 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): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed 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 RustDev release test (local only) appear?
The Rust Server Trends lists that take in RustDev release test (local only) are: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Connecting
How do you connect to RustDev release test (local only)?
Enter client.connect 38.64.18.70:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust 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.