Offline 193.47.34.190:28015 checked 34d ago
SoloOffline2
Connect
srv = rust.server("193.47.34.190:28016")
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 bestTop 61% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 24 Sep, 17:39 UTC34d ago | 1 | NaN | running | 1 |
# 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
- 193.47.34.190:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 24 Sep 2026, 23:23 UTC
- hostname
- –
- first seen
- 20 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 · 149 on average | 172/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 128/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 169/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 82/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 86 on average | 100/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 86 on average | 244/700 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does SoloOffline2 rank?
Rank #13,680 on seven-day player hours for SoloOffline2, within the top 61% of all ranked servers.
How full does SoloOffline2 run?
SoloOffline2 returns no live count at this refresh, having last been seen 34 days 15 hours ago.
Server data
What Rust version does SoloOffline2 run?
Rust network protocol 2633 and build 163794 on Windows is what SoloOffline2 runs. Joining needs the same protocol on your game; Steam handles the update.
Is SoloOffline2 up, and what does its uptime show?
Offline now for SoloOffline2, last seen 34 days 15 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 20 September 2026.
Which location does SoloOffline2 run from?
For SoloOffline2, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 193.47.34.190:28015.
Map and rules
Which rules apply on SoloOffline2, and what settings?
The name SoloOffline2 carries no gather rate. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. Anti-cheat status: VAC on.
Which map has SoloOffline2 loaded?
The game generates its map: procedural, on SoloOffline2.
Wipe data
On what schedule does SoloOffline2 wipe?
A rhythm cannot be read from the wipes of SoloOffline2 on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 34 days 15 hours ago, and that is the one in play.
What is wipe day on SoloOffline2 like?
The average peak over recent wipes is 1 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Which Rust Data filters and lists contain SoloOffline2?
On Rust Data, SoloOffline2 appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on SoloOffline2?
These tags are published by SoloOffline2 and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): Slot count: 1; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs163794 (Build): The server runs build 163794; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
What is the way into SoloOffline2?
Enter client.connect 193.47.34.190:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.