Station XX-15444 · no signal
Roundtrace private lifecycle test
Offline 47.199.60.2:28028 checked 41d ago
- Players now
- 0/ 2
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,444
- no region published
- Last wipe
- 41d ago
- no schedule published
- Next wipe
- –
- no wipe seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 2 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 bestWipe 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 Roundtrace private lifecycle test?
A procedural map runs on Roundtrace private lifecycle test, generated by the game.
Which settings and rules apply on Roundtrace private lifecycle test?
The name of Roundtrace private lifecycle test gives no gather rate. Groups hold up to 8 players, which is the default for the game. In survival mode, gather, build and raid in the standard game. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.
Player counts
How many players are recorded on Roundtrace private lifecycle test right now?
Roundtrace private lifecycle test is not responding at this moment and is offline, last seen 41 days ago.
How does Roundtrace private lifecycle test rank against other Rust servers?
On player hours for the past week, Roundtrace private lifecycle test sits at #15,444, which puts it inside the top – of every ranked server.
Server details
How reliably does Roundtrace private lifecycle test stay online?
As recorded now, Roundtrace private lifecycle test is not reachable, the last contact having been 41 days ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 18 September 2026 it was recorded for the first time by Rust Server Trends.
Where in the world is Roundtrace private lifecycle test hosted?
A region is not published by Roundtrace private lifecycle test. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 47.199.60.2:28028 is the address it uses.
What build of Rust does Roundtrace private lifecycle test use?
Rust network protocol 2633 and build 164530 on Windows is what Roundtrace private lifecycle test runs. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
On what timetable does Roundtrace private lifecycle test run its wipes?
On record so far are too few of Roundtrace private lifecycle test's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 41 days is how long the current world has been running.
Server tags
What do the server tags on Roundtrace private lifecycle test mean?
Tags published by Roundtrace private lifecycle test and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp2 (Max players): The server has 2 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2633 (Protocol): Your game needs to be on protocol 2633 to join; cs164530 (Build): Game build: 164530; 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): Oxide (uMod) is the plugin framework running 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 Roundtrace private lifecycle test appear?
The Rust Server Trends lists that take in Roundtrace private lifecycle test 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 Roundtrace private lifecycle test?
Enter client.connect 47.199.60.2:28028 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.