Offline 208.88.69.27:28904 checked 21d ago
osmium dev w17-dev (local)
Connect
srv = rust.server("208.88.69.27:28905")
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 24, 0 hours in, with 6 in the queue.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 8 Oct, 11:05 UTC21d ago | 24+6 queue | NaN | running | 24 |
# 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:28904
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 8 Oct 2026, 11:05 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 · 151 on average | 144/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 133/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 197/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 95 on average | 82/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 89 on average | 228/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 351/350 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does osmium dev w17-dev (local) rank?
Over the last seven days osmium dev w17-dev (local) sits at #15,874 on player hours, in the top 72% of ranked servers.
What population does osmium dev w17-dev (local) carry?
The current row shows osmium dev w17-dev (local) offline; the last response was 21 days 4 hours ago.
Server facts
What Rust version does osmium dev w17-dev (local) run?
Version Rust network protocol 2634 and build 167231 on Linux is reported by osmium dev w17-dev (local). Joining needs the same protocol on your game; Steam handles the update.
How reliable is osmium dev w17-dev (local), and is it up?
The latest sample has osmium dev w17-dev (local) offline, with a last sighting 21 days 4 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 8 October 2026.
Where does osmium dev w17-dev (local) sit?
There is no region published for osmium dev w17-dev (local). Rust Data does not look up where the machine stands; it shows where a server says it is. 208.88.69.27:28904 is its address.
Rules, settings, map
Which settings and rules does osmium dev w17-dev (local) run?
You will not find a gather rate in the string osmium dev w17-dev (local). No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. VAC is not running; Valve's anti-cheat is off.
Which map has osmium dev w17-dev (local) selected?
osmium dev w17-dev (local) runs a procedural map, which the game generates.
Wipe schedule
When does osmium dev w17-dev (local) wipe, and on what schedule?
Too few wipes are on record for osmium dev w17-dev (local) to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 21 days 7 hours ago.
On osmium dev w17-dev (local), what happens on wipe day?
Across recent wipes the busiest point averaged 24 players. 0 hours after the latest wipe the crowd peaked, and 6 more were queued.
Lists and tags
Where does osmium dev w17-dev (local) appear among Rust Data lists and filters?
The Rust Data lists that osmium dev w17-dev (local) fits are: 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 osmium dev w17-dev (local) hold?
These tags are published by osmium dev w17-dev (local) and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp4 (Max players): 4 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167231 (Build): The server runs build 167231; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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
How can I connect to osmium dev w17-dev (local)?
The manual route: launch Rust, F1, then client.connect 208.88.69.27:28904. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.