Offline 208.88.69.27:28870 checked 6d ago
osmium dev rel044-contracts (local)
Connect
srv = rust.server("208.88.69.27:28871")
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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. 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 22 Oct, 18:39 UTC6d ago | 0 | NaN | running | 0 |
| 1 | Thu 22 Oct, 04:19 UTC6d ago | 0 | NaN | 0.6 days | 0 |
| 2 | Sat 10 Oct, 02:49 UTC18d ago | 0 | NaN | 12.1 days | 0 |
| 3 | Thu 8 Oct, 11:12 UTC20d ago | 0 | NaN | 1.7 days | 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:28870
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 22 Oct 2026, 18:39 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 · 157 on average | 61/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 134/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 61/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 92 on average | 51/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 16/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 9/1000 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does osmium dev rel044-contracts (local) rank?
Rank #15,344 on seven-day player hours for osmium dev rel044-contracts (local), within the top 69% of all ranked servers.
How full does osmium dev rel044-contracts (local) run?
Offline now for osmium dev rel044-contracts (local), with the last sample 6 days 4 hours ago. Over the last seven days it averaged 0 players.
About the server
Which Rust version is osmium dev rel044-contracts (local) on?
The build is Rust network protocol 2634 and build 167231 on Linux, run by osmium dev rel044-contracts (local). Joining needs the same protocol on your game; Steam handles the update.
How reliable is osmium dev rel044-contracts (local), and is it up?
Offline now for osmium dev rel044-contracts (local), last seen 6 days 4 hours ago. Over the last 7 full days the hours up number 2 of 168, 1%. Its earliest recorded date in Rust Data is 8 October 2026.
Which location does osmium dev rel044-contracts (local) run from?
For osmium dev rel044-contracts (local), no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 208.88.69.27:28870.
Map and rules
Which settings and rules does osmium dev rel044-contracts (local) run?
The name osmium dev rel044-contracts (local) carries no gather rate. The group limit sits at the default of 8 players. survival is the game mode here, and the usual game, with gathering, building and raiding. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
What is the map on osmium dev rel044-contracts (local)?
osmium dev rel044-contracts (local) runs a procedural map, which the game generates.
Wipe data
When does osmium dev rel044-contracts (local) wipe, and on what schedule?
No next wipe can be predicted for osmium dev rel044-contracts (local), which wipes at irregular times. 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 6 days 4 hours ago.
What is wipe day on osmium dev rel044-contracts (local) like?
Across recent wipes the busiest point averaged 0 players. The crowd on the latest wipe topped out 0 hours after it began.
Lists and tags
Where does osmium dev rel044-contracts (local) appear among Rust Data lists and filters?
These Rust Data lists include osmium dev rel044-contracts (local): Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Which meanings do the tags on osmium dev rel044-contracts (local) hold?
These tags are published by osmium dev rel044-contracts (local) and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp4 (Max players): Slot count: 4; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167231 (Build): Build number: 167231; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game; osmium (Custom tag): This tag comes from the owner or a plugin, not from Rust itself. 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 to join osmium dev rel044-contracts (local)?
The manual route: launch Rust, F1, then client.connect 208.88.69.27:28870. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.