Offline 208.88.69.27:28855 checked 6d ago
osmium dev rustedit-check (local)
Connect
srv = rust.server("208.88.69.27:28856")
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 · 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 22 Oct, 18:49 UTC6d 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
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 208.88.69.27:28855
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 22 Oct 2026, 18:57 UTC
- hostname
- –
- first seen
- 22 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 | 109/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 125/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 167/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 52/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 5/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 22/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does osmium dev rustedit-check (local) rank?
Player hours over seven days put osmium dev rustedit-check (local) at #15,335, in the top 69% of the ranked set.
How full does osmium dev rustedit-check (local) run?
The current row shows osmium dev rustedit-check (local) offline; the last response was 6 days 13 hours ago. Over the last seven days it averaged 0 players.
About the server
What is the Rust version on osmium dev rustedit-check (local)?
Rust network protocol 2634 and build 167231 on Linux is what osmium dev rustedit-check (local) runs. The protocol has to match before you can join, and Steam does the updating.
Is osmium dev rustedit-check (local) up, and what does its uptime show?
The latest sample has osmium dev rustedit-check (local) offline, with a last sighting 6 days 13 hours ago. Uptime of 0% across the last 6 full days: 0 hours of 144. Rust Data logged it first on 22 October 2026.
In which location is osmium dev rustedit-check (local) hosted?
No region is published by osmium dev rustedit-check (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:28855 is its address.
Rules, settings, map
Which settings and rules does osmium dev rustedit-check (local) run?
No gather rate appears in the name: osmium dev rustedit-check (local). No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. Anti-cheat status: VAC on.
Wipe data
When does osmium dev rustedit-check (local) wipe, and on what schedule?
A rhythm cannot be read from the wipes of osmium dev rustedit-check (local) 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 6 days 13 hours ago, and that is the one in play.
What is wipe day on osmium dev rustedit-check (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 rustedit-check (local), and which filters?
These Rust Data lists include osmium dev rustedit-check (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 rustedit-check (local) hold?
The game's server browser reads these tags from osmium dev rustedit-check (local): gmrust (Game mode): Rust survival in its standard form; mp4 (Max players): Slot count: 4; 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): Build number: 167231; ptrak (Networking): Standard network layer for Rust: RakNet; $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; 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 rustedit-check (local)?
In Rust, F1 opens the console: type client.connect 208.88.69.27:28855. Launch Rust on this page does the same by opening the game through Steam and connecting.