RUST METRICSFlight deck · live data
Data live Servers11,705 Players41,937 Populated3,034 Fresh wipes 3 h101 Scan5 min
‹ All servers208.88.69.27:28785
Offline Full Queue Fresh wipe Wipe due No query

osmium release selftest (local)

Offline 208.88.69.27:28785 checked 12d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 1 2 3 4 PAX 0 /4

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,102top 70%
Last wipe12d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k16 Oct17 Oct19 Oct20 Oct22 Oct23 Oct

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

PLAN

Wipe schedule

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What wipe timing does osmium release selftest (local) follow?

Its rhythm cannot be told from the wipes of osmium release selftest (local) on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 12 days 12 hours ago the current world was made.

Tag meanings

How should you read the tags on osmium release selftest (local)?

Tags published by osmium release selftest (local), read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp4 (Max players): 4 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168268 (Build): The server runs game build 168268; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does osmium release selftest (local) appear in Rust Metrics lists and filters?

On Rust Metrics, osmium release selftest (local) sits in these lists: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Player count

Where does osmium release selftest (local) sit in the rankings?

Player hours over seven days put osmium release selftest (local) at #15,102, in the top 70% of all ranked servers.

How full does osmium release selftest (local) get?

osmium release selftest (local) is not responding; status offline, last seen 12 days 12 hours ago.

Server details

Where does osmium release selftest (local) sit?

No region comes from osmium release selftest (local). Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 208.88.69.27:28785.

What Rust version is osmium release selftest (local) on?

Version check: Rust network protocol 2635 and build 168268 on Linux, run by osmium release selftest (local). Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on osmium release selftest (local), and is it online?

Check: connection. osmium release selftest (local) is offline at this moment. Last contact was 12 days 12 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 16 October 2026.

Rules and settings

What rules does osmium release selftest (local) enforce, and what are its settings?

Reading the name gives no gather rate for osmium release selftest (local). 8 players per group, the default value. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. VAC is on. That is Valve's anti-cheat.

What map is osmium release selftest (local) on?

Check: map. Procedural, generated by the game, on osmium release selftest (local).

Join

How do you connect to osmium release selftest (local)?

Check: join. Open Rust, press F1, then enter client.connect 208.88.69.27:28785. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp4,ptrak,$r?,v2635,gmrust,cs168268,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp4
Max players 4 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168268
Build The server runs game build 168268.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

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.