Offline 208.88.69.27:28745 checked 21d ago
osmium dev w3-oxide (local)
Connect
srv = rust.server("208.88.69.27:28746")
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 best
Top 72% 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 8 Oct, 00:28 UTC21d ago | 0 | NaN | running | 0 |
# 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
- 208.88.69.27:28745
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 8 Oct 2026, 00:54 UTC
- hostname
- –
- first seen
- 8 Oct 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 | 183/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 127/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 182/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 85/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 86 on average | 343/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 86 on average | 246/700 |
Quick answers
From the figures on this page.
Population data
How does osmium dev w3-oxide (local) compare in the rankings?
Over the last seven days osmium dev w3-oxide (local) sits at #15,922 on player hours, in the top 72% of ranked servers.
How many players does osmium dev w3-oxide (local) hold at once?
Offline now for osmium dev w3-oxide (local), with the last sample 21 days 14 hours ago.
About the server
Which Rust version is osmium dev w3-oxide (local) on?
Rust network protocol 2634 and build 167058 on Linux is what osmium dev w3-oxide (local) runs. Steam updates your game for you, but the protocol must match to join.
How reliable is osmium dev w3-oxide (local), and is it online now?
osmium dev w3-oxide (local) is offline at this refresh; the last response came 21 days 14 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 8 October 2026.
Which location does osmium dev w3-oxide (local) run from?
For osmium dev w3-oxide (local), no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 208.88.69.27:28745 is its address.
Rules, settings, map
What rules and settings are recorded for osmium dev w3-oxide (local)?
The name osmium dev w3-oxide (local) carries no gather rate. The group limit sits at the default of 8 players. 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 osmium dev w3-oxide (local) selected?
The game generates its map: procedural, on osmium dev w3-oxide (local).
Wipe data
When does osmium dev w3-oxide (local) wipe, and on what schedule?
The record for osmium dev w3-oxide (local) holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 21 days 14 hours ago.
What is wipe day on osmium dev w3-oxide (local) like?
Recent wipes averaged 0 players at their peak. Peak population on the latest wipe came 0 hours in.
Lists and tags
Which lists on Rust Data hold osmium dev w3-oxide (local), and which filters?
The Rust Data lists that osmium dev w3-oxide (local) fits are: 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.
Which meanings do the tags on osmium dev w3-oxide (local) hold?
The game's server browser reads these tags from osmium dev w3-oxide (local): gmrust (Game mode): Survival play, standard Rust; mp4 (Max players): The server lists 4 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167058 (Build): Build number: 167058; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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 osmium dev w3-oxide (local)?
Enter client.connect 208.88.69.27:28745 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.