Rust Data LabData lab · live
Live readings Servers11,824 Players75,694 Populated3,728 Fresh wipes · 3h230 Sampled every 5 min

Element card · group Modded · atomic number 15,349, its rank

osmium dev extcheck-managed (local)

Offline 208.88.69.27:28841 checked 7d ago

moddedoxide
Join the experiment
Atomic mass · players now 0/ 4 0% full Room to join
7-day average0peak –
Rank · atomic number#15,349top 69%
Last wipe7d agono schedule published
Next wipe–too few wipes seen yet
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
No hourly history yet.

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
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.

Result 03

Rank

Result

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.

Reaction kinetics

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 peak0players, 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.

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 22 Oct, 04:38 UTC7d ago 0 – 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
  1. 1 Sh ShockRust | Bl… 195
    ShockRust | Blue | NoLimit no group limit · 149 on average 195/ 500
  2. 2 Ми МИНИ-КАРТА 2Х … 129
    МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average 129/ 100
  3. 3 Ru 404 RUST 2Х|ДЛ… 82
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 94 on average 82/ 700
  4. 4 Ru RustSpain.com … 32
    RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average 32/ 200
  5. 5 Ru 404 RUST 2Х|ДЛ… 282
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 85 on average 282/ 700
  6. 6 Ru 404 RUST 2Х|ДЛ… 30
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average 30/ 1,000

Quick answers

from the figures on this page

Map and rules

What map is in play on osmium dev extcheck-managed (local)?

Generated by the game, the map on osmium dev extcheck-managed (local) is procedural.

What rules has osmium dev extcheck-managed (local) set, and what settings are in force?

The name of osmium dev extcheck-managed (local) carries no gather rate. Eight players per group is the limit, the game's default. Play runs as survival, raiding, building and gathering: the standard game. Fighting and raiding between players are allowed. The server browser lists it under Modded, where plugins or settings change the game. Oxide plugins are running on it. Anti-cheat is on: Valve's VAC.

Server details

In what location does osmium dev extcheck-managed (local) sit?

Nothing about a region is published by osmium dev extcheck-managed (local). The location shown is the one a server states; Rust Data Lab does not check where the machine actually stands. 208.88.69.27:28841 is the address it uses.

On what Rust version does osmium dev extcheck-managed (local) operate?

On Linux, osmium dev extcheck-managed (local) is running Rust network protocol 2634 and build 167231. Your game needs to match the protocol to join, and Steam updates it automatically.

How dependable is osmium dev extcheck-managed (local) for staying online?

Right now osmium dev extcheck-managed (local) is offline, with its last appearance 7 days 9 hours ago. For the last 6 full days, 0 of 144 hours were online, giving 0% uptime. The first sighting by Rust Data Lab was on 22 October 2026.

Wipes and resets

What is the wiping pattern on osmium dev extcheck-managed (local)?

The record holds too few of osmium dev extcheck-managed (local)'s wipes to show its rhythm. The monthly force wipe resets every Rust server; it next occurs on Thursday 5 November at 19:00 UTC. 7 days 9 hours ago the current world was made.

How does osmium dev extcheck-managed (local) look on the day of a wipe?

At their busiest, recent wipes averaged 0 players. The latest wipe's peak fell 0 hours after it began.

Where it appears

How should you read the tags on osmium dev extcheck-managed (local)?

These are the tags osmium dev extcheck-managed (local) makes public for the server browser to read: gmrust (Game mode): Survival in the standard Rust style; mp4 (Max players): Player slots: 4; ts8 (Group limit): 8 per team, the default the game ships with; v2634 (Protocol): The server runs protocol 2634, so your game needs the same version; cs167231 (Build): It runs build 167231; ptrak (Networking): This runs on RakNet, the standard layer; $r? (Region code): The region field is left blank; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Because plugins or settings change the game, it is filed under Modded; osmium (Custom tag): Not a standard Rust tag, so either a plugin or the owner applied it. The tags carry more as well: current players, the queue and when the world was made, all shown at the top of this page.

Where among the Rust Data Lab lists and filters does osmium dev extcheck-managed (local) come up?

These themed Rust Data Lab lists carry osmium dev extcheck-managed (local): Modded Rust servers, measured. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Population

Against other Rust servers, where does osmium dev extcheck-managed (local) place?

Player hours over the last week put osmium dev extcheck-managed (local) at #15,349, inside the top 69% of ranked servers.

What does the current player count on osmium dev extcheck-managed (local) tell you?

osmium dev extcheck-managed (local) is offline at the moment; the last sighting was 7 days 9 hours ago. Over seven days the mean player count is 0.

Connection

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

In Rust, press F1 and enter client.connect 208.88.69.27:28841. Or click Launch Rust here to open Rust via Steam and connect automatically.

Server tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust style.
mp4
Max players Player slots: 4.
ts8
Group limit 8 per team, the default the game ships with.
v2634
Protocol The server runs protocol 2634, so your game needs the same version.
cs167231
Build It runs build 167231.
ptrak
Networking This runs on RakNet, the standard layer.
$r?
Region code The region field is left blank.

Mods and access

^o
Oxide Plugins run through Oxide (uMod).
^z
Modded Because plugins or settings change the game, it is filed under Modded.

Other

osmium
Custom tag Not a standard Rust tag, so either a plugin or the owner applied it.

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.