Rust Server TrendsSeismic network · station log
Recording Stations11,655 Players43,200 Active2,897 Wipes · 3 h105 48 h

Station XX-15886 · no signal

osmium dev w14 (local)

Offline 208.88.69.27:28860 checked 21d ago

moddedoxide
Connect
Players now
0/ 4
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,886
top 72%
Last wipe
21d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15886 · 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
15k10k15k20k8 Oct9 Oct11 Oct12 Oct14 Oct15 Oct

Top 72% 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 8 Oct, 11:42 UTC21d 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 · 151 on average
20/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
123/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 122 on average
39/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 97 on average
5/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 94 on average
23/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 87 on average
96/ 200
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on osmium dev w14 (local)?

The map on osmium dev w14 (local) is procedural, produced by the game.

Which settings and rules apply on osmium dev w14 (local)?

The name of osmium dev w14 (local) gives no gather rate. At the game's default, groups can have up to 8 players. survival is the game mode, the usual game of gathering, building and raiding. You can raid and fight other players here. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Oxide. Anti-cheat is on: VAC, from Valve.

Population

What is the current population on osmium dev w14 (local)?

A reading taken now finds osmium dev w14 (local) offline; the most recent activity was 21 days 15 hours ago.

How does osmium dev w14 (local) rank against other Rust servers?

The last seven days of player hours place osmium dev w14 (local) at #15,886, in the top 72% of all ranked servers.

Server details

How reliably does osmium dev w14 (local) stay online?

As recorded now, osmium dev w14 (local) is not reachable, the last contact having been 21 days 15 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. 8 October 2026 is when Rust Server Trends first recorded it.

Which region does osmium dev w14 (local) run from?

Nothing about a region comes from osmium dev w14 (local). The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 208.88.69.27:28860 is the address it uses.

Which Rust version is osmium dev w14 (local) running?

Rust network protocol 2634 and build 167231 on Linux is what osmium dev w14 (local) runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe pattern

What does wipe day look like on osmium dev w14 (local)?

0 players, on average, was the busiest crowd at its recent wipes. 0 hours into the latest wipe, the crowd reached its peak.

How often does osmium dev w14 (local) wipe, and on which days?

The rhythm of osmium dev w14 (local) cannot yet be told: too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 21 days 15 hours.

Tags

What do the server tags on osmium dev w14 (local) mean?

The game's server browser reads the tags osmium dev w14 (local) publishes: gmrust (Game mode): You'll find standard Rust survival here; mp4 (Max players): Slots: 4; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167231 (Build): It runs game build 167231; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does osmium dev w14 (local) appear?

The Rust Server Trends lists that take in osmium dev w14 (local) are: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Join the server

What steps get you onto osmium dev w14 (local)?

You can connect by pressing F1 in Rust and typing client.connect 208.88.69.27:28860 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

Game

gmrust
Game mode You'll find standard Rust survival here.
mp4
Max players Slots: 4.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs167231
Build It runs game build 167231.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code A region code has not been set.

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.

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.