RUST METRICSFlight deck · live data
Data live Servers11,874 Players88,657 Populated4,001 Fresh wipes 3 h162 Scan5 min
‹ All servers34.91.74.176:28015
Offline Full Queue Fresh wipe Wipe due No query

oxide-observation

Offline 34.91.74.176:28015 checked 41d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

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,468no region published
Last wipe41d 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
15k10k15k20k20 Sep21 Sep22 Sep23 Sep
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

Wipe schedule

When does oxide-observation wipe?

Its rhythm cannot be told from the wipes of oxide-observation on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 41 days 16 hours ago the current world was made.

Tags

Which tags does oxide-observation carry, and what do they mean?

Tags published by oxide-observation, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163794 (Build): The server runs game build 163794; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does oxide-observation appear in Rust Metrics lists and filters?

These Rust Metrics lists carry oxide-observation: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Population

What position does oxide-observation hold among Rust servers?

Ranking for oxide-observation: #15,468 on seven-day player hours, top – of all ranked servers.

What player count does oxide-observation carry?

Status for oxide-observation: offline. Last seen 41 days 16 hours ago.

Server details

Where does oxide-observation sit?

Reading: location. oxide-observation gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 34.91.74.176:28015.

What Rust version is oxide-observation on?

Reading: oxide-observation, Rust network protocol 2633 and build 163794, Linux. Matching protocol is required to join. Let Steam update your game.

Is oxide-observation up, and how often does it stay up?

Reading: offline. oxide-observation last answered 41 days 16 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 16 September 2026.

Settings and map

How is oxide-observation configured, and what rules are in force?

Check: gather rate. The name oxide-observation does not state one. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.

What map is oxide-observation on?

The game generates a procedural map for oxide-observation.

Connection

What do you do to join oxide-observation?

Press F1 in Rust and enter client.connect 34.91.74.176:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2633,gmrust,cs163794,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players The server holds 10 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Match the game version: protocol 2633 is required.
cs163794
Build The server runs game build 163794.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Modded: plugins or settings depart from the stock game.

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.