Rust Server TrendsSeismic network · station log
Recording Stations11,617 Players40,309 Active2,963 Wipes · 3 h87 48 h

Station XX-15339 · no signal

osmium dev rustedit-check (local)

Offline 208.88.69.27:28855 checked 6d ago

moddedoxide
Connect
Players now
0/ 4
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,339
top 69%
Last wipe
6d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15339 · 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

01234+0h+9h+19h+28h+38h+47h

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, 18:49 UTC6d 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 · 150 on average
78/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
132/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 118 on average
124/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 93 on average
40/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
3/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
15/ 1000
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which settings and rules apply on osmium dev rustedit-check (local)?

The name of osmium dev rustedit-check (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. You can raid and fight other players here. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Oxide. Anti-cheat is on: VAC, from Valve.

Population

How many players are recorded on osmium dev rustedit-check (local) right now?

A reading taken now finds osmium dev rustedit-check (local) offline; the most recent activity was 6 days 12 hours ago. The population averaged 0 players over the past week.

How does osmium dev rustedit-check (local) rank against other Rust servers?

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

Server facts

How reliably does osmium dev rustedit-check (local) stay online?

As recorded now, osmium dev rustedit-check (local) is not reachable, the last contact having been 6 days 12 hours ago. It was up 0% of the time across the last 6 full days: 0 of 144 hours. 22 October 2026 is when Rust Server Trends first recorded it.

Which region does osmium dev rustedit-check (local) run from?

No region is published by osmium dev rustedit-check (local). Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 208.88.69.27:28855.

Which Rust version is osmium dev rustedit-check (local) running?

osmium dev rustedit-check (local) is running Rust network protocol 2634 and build 167231 on a machine with Linux. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe schedule

What does wipe day look like on osmium dev rustedit-check (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 rustedit-check (local) wipe, and on which days?

Too few wipes of osmium dev rustedit-check (local) are on record yet to show its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 6 days 12 hours is how long the current world has been running.

Tags

What do the server tags on osmium dev rustedit-check (local) mean?

The game's server browser reads the tags osmium dev rustedit-check (local) publishes: gmrust (Game mode): Survival in standard Rust; mp4 (Max players): Slots: 4; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167231 (Build): The game build is 167231; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; osmium (Custom tag): The owner or a plugin applied this tag, which isn't part of standard Rust. 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 rustedit-check (local) appear?

The Rust Server Trends lists that take in osmium dev rustedit-check (local) are: Modded Rust servers, tracked live. You will find it 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.

How to join

How do you connect to osmium dev rustedit-check (local)?

To join, enter client.connect 208.88.69.27:28855 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for 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 Slots: 4.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2634
Protocol Your game needs to be on protocol 2634 to join.
cs167231
Build The game build is 167231.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code The server has no region code.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded The game is changed by plugins or settings, placing it under Modded.

Other

osmium
Custom tag The owner or a plugin applied this tag, which isn't part of standard Rust.

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.