Offline 208.88.69.27:28990 checked 21d ago
osmium dev render-c (local)
Connect
srv = rust.server("208.88.69.27:28991")
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 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe 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
- 208.88.69.27:28990
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 8 Oct 2026, 14:34 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 | 78/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 135/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 131/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 42/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 91 on average | 135/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 347/350 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does osmium dev render-c (local) rank?
Player hours over seven days put osmium dev render-c (local) at #15,848, in the top 72% of the ranked set.
How full does osmium dev render-c (local) run?
The current row shows osmium dev render-c (local) offline; the last response was 21 days 6 hours ago.
Server facts
What Rust version does osmium dev render-c (local) run?
Rust network protocol 2634 and build 167231 on Linux is what osmium dev render-c (local) runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is osmium dev render-c (local), and is it online now?
The latest sample has osmium dev render-c (local) offline, with a last sighting 21 days 6 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 8 October 2026.
Which location does osmium dev render-c (local) run from?
No region is published by osmium dev render-c (local). 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:28990 is its address.
Rules, settings, map
Which rules apply on osmium dev render-c (local), and what settings?
The name osmium dev render-c (local) carries no gather rate. The group limit sits at the default of 8 players. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. Anti-cheat status: VAC on.
Which map has osmium dev render-c (local) loaded?
A procedural map runs on osmium dev render-c (local), generated by the game.
Wipes and dates
When does osmium dev render-c (local) wipe, and on what schedule?
Too few wipes are on record for osmium dev render-c (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 6 hours ago.
Lists and tags
Which lists on Rust Data hold osmium dev render-c (local), and which filters?
These Rust Data lists include osmium dev render-c (local): 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 render-c (local) hold?
The game's server browser reads these tags from osmium dev render-c (local): gmrust (Game mode): Survival play, standard Rust; mp4 (Max players): 4 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167231 (Build): Recorded game build: 167231; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way into osmium dev render-c (local)?
In Rust, F1 opens the console: type client.connect 208.88.69.27:28990. Launch Rust on this page does the same by opening the game through Steam and connecting.