Rust Server TrendsSeismic network · station log
Recording Stations11,668 Players48,663 Active3,138 Wipes · 3 h118 48 h

Station XX-15349 · no signal

osmium dev extcheck-managed (local)

Offline 208.88.69.27:28841 checked 7d ago

moddedoxide
Connect
Players now
0/ 4
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,349
top 69%
Last wipe
7d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15349 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 4 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k22 Oct23 Oct25 Oct26 Oct28 Oct29 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak
0players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Thu 22 Oct, 04:38 UTC7d ago M0.0steady 0 – – running 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 149 on average
107/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
122/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 118 on average
182/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 93 on average
60/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
5/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
24/ 1000
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on osmium dev extcheck-managed (local)?

osmium dev extcheck-managed (local) uses a procedural map, which the game generates.

Which settings and rules apply on osmium dev extcheck-managed (local)?

The name of osmium dev extcheck-managed (local) gives no gather rate. Groups hold up to 8 players, which is the default for the game. In survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Oxide. VAC, Valve's anti-cheat, is switched on.

Population

What is the current population on osmium dev extcheck-managed (local)?

A reading taken now finds osmium dev extcheck-managed (local) offline; the most recent activity was 7 days 4 hours ago. Averaged across the last seven days, the population was 0 players.

How does osmium dev extcheck-managed (local) rank against other Rust servers?

On player hours for the past week, osmium dev extcheck-managed (local) sits at #15,349, which puts it inside the top 69% of every ranked server.

Operator and location

How reliably does osmium dev extcheck-managed (local) stay online?

As recorded now, osmium dev extcheck-managed (local) is not reachable, the last contact having been 7 days 4 hours ago. Of the 144 hours in the last 6 full days, it was up for 0, or 0% of the time. On 22 October 2026 it was recorded for the first time by Rust Server Trends.

Where in the world is osmium dev extcheck-managed (local) hosted?

Nothing about a region comes from osmium dev extcheck-managed (local). Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 208.88.69.27:28841 is the address it uses.

What build of Rust does osmium dev extcheck-managed (local) use?

osmium dev extcheck-managed (local) is running Rust network protocol 2634 and build 167231 on a machine with Linux. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe day

What does wipe day look like on osmium dev extcheck-managed (local)?

On average, the busiest point of its recent wipes drew 0 players. 0 hours into the latest wipe, the crowd reached its peak.

How often does osmium dev extcheck-managed (local) wipe, and on which days?

On record so far are too few of osmium dev extcheck-managed (local)'s wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The present world dates from 7 days 4 hours.

Lists and tags

What do the server tags on osmium dev extcheck-managed (local) mean?

Tags published by osmium dev extcheck-managed (local) and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp4 (Max players): 4 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167231 (Build): Game build: 167231; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; osmium (Custom tag): A custom tag, not standard Rust: set by the owner or a plugin. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does osmium dev extcheck-managed (local) appear?

These Rust Server Trends lists include osmium dev extcheck-managed (local): Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

How to join

What steps get you onto osmium dev extcheck-managed (local)?

You can connect by pressing F1 in Rust and typing client.connect 208.88.69.27:28841 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp4,ptrak,$r?,v2634,gmrust,cs167231,ts8,^o^z,osmium

Game

gmrust
Game mode Survival in standard Rust.
mp4
Max players 4 slots are available.
ts8
Group limit This uses the game default of 8 per team.
v2634
Protocol Your game needs to be on protocol 2634 to join.
cs167231
Build Game build: 167231.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The server has no region code.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded Plugins or settings alter the game, so it's listed under Modded.

Other

osmium
Custom tag A custom tag, not standard Rust: set by the owner or a plugin.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.