Offline 47.199.60.2:28028 checked 39d ago
Roundtrace private lifecycle test
Connect
srv = rust.server("47.199.60.2:28030")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestWipe schedule
srv.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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# Peak: the most players in the first 48 hours. 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 47.199.60.2:28028
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 18 Sep 2026, 21:51 UTC
- hostname
- –
- first seen
- 18 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 156 on average | 104/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 122/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 113/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 45/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 6/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 20/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does Roundtrace private lifecycle test rank?
Rank #15,444 on seven-day player hours for Roundtrace private lifecycle test, within the top – of all ranked servers.
How full does Roundtrace private lifecycle test run?
Offline now for Roundtrace private lifecycle test, with the last sample 39 days 9 hours ago.
Server data
What Rust version does Roundtrace private lifecycle test run?
The build is Rust network protocol 2633 and build 164530 on Windows, run by Roundtrace private lifecycle test. The protocol has to match before you can join, and Steam does the updating.
Is Roundtrace private lifecycle test up, and what does its uptime show?
Roundtrace private lifecycle test is offline at this refresh; the last response came 39 days 9 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 18 September 2026.
Which location does Roundtrace private lifecycle test run from?
There is no region published for Roundtrace private lifecycle test. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 47.199.60.2:28028.
Rules, settings, map
What rules and settings are recorded for Roundtrace private lifecycle test?
No gather rate appears in the name: Roundtrace private lifecycle test. The group limit sits at the default of 8 players. survival is the game mode here, and gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has Roundtrace private lifecycle test loaded?
The game generates its map: procedural, on Roundtrace private lifecycle test.
Wipe schedule
When does Roundtrace private lifecycle test wipe, and on what schedule?
Too few wipes are on record for Roundtrace private lifecycle test to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 39 days 9 hours ago, and that is the one in play.
Lists and tags
Which Rust Data filters and lists contain Roundtrace private lifecycle test?
These Rust Data lists include Roundtrace private lifecycle test: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on Roundtrace private lifecycle test hold?
These tags are published by Roundtrace private lifecycle test and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp2 (Max players): The server lists 2 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs164530 (Build): Recorded game build: 164530; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way into Roundtrace private lifecycle test?
The manual route: launch Rust, F1, then client.connect 47.199.60.2:28028. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.