Rust HeatmapInfrared · players
IR live Players78,222 Servers11,801 Warm3,772 Fresh wipes · 3h109 Frameevery 5 min
‹ All serversThermal scan
REC Thermal scan · 48 h Sp1 0° now Linear · 0–10° · slots

oxide-observation

Offline 34.91.74.176:28015 checked 42d ago

moddedoxide
Sp1 · players now 0/ 10
0% full
Li1 · players, the last 48 hours · hourly average, UTC
No hourly readings in the last 48 hours
0
7-day average
peak –
#15,468
rank
no region published
42d ago
last wipe
no schedule published
–
next wipe
no wipe seen yet
UTC checked 42d ago

Li2Players

No hourly history yet.

Hourly average and peak, UTC.

Li3Server 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.

Li4Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep21 Sep22 Sep23 Sep

Bx1Wipe schedule

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

Bx2Wipes

newest first · each peak a flare-up, on one √ span to its biggest
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.

Bx6Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit
no group limit · 157 on average
132 / 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10
EU · groups of 8+ · weekly · 127 on average
128 / 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10
EU · groups of 16+ · weekly · 115 on average
148 / 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10
EU · groups of 16+ · monthly · 90 on average
117 / 700
RustSpain.com | EU Main
EU · groups of 12+ · weekly · 88 on average
33 / 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10
EU · groups of 16+ · monthly · 84 on average
33 / 1000

LogQuick answers

from the figures on this page

Wipe schedule

What is the wipe schedule on oxide-observation?

Its rhythm cannot yet be told: too few of oxide-observation's wipes are on record. Next on Thursday 5 November at 19:00 UTC, the monthly force wipe resets every Rust server. The world in play now was made 42 days 16 hours ago.

Population

How busy is oxide-observation?

Last seen 42 days 16 hours ago, oxide-observation is offline at the moment.

How does oxide-observation rank against other Rust servers?

The top – of ranked servers includes oxide-observation, at #15,468 for player hours over the last seven days.

Rules and settings

Which map does oxide-observation run?

A procedural map, generated by the game, runs on oxide-observation.

What are the rules and settings on oxide-observation?

No gather rate appears in the name oxide-observation. Groups can contain up to 8 players, the default in the game. survival is the game mode, gather, build and raid in the standard game. You can fight other players and raid their bases. The server browser lists it as Modded: plugins or settings change the game. Oxide plugins run on this server. The server has VAC, Valve's anti-cheat, turned on.

Location and uptime

Which version of Rust does oxide-observation run?

Rust network protocol 2633 and build 163794 is the build oxide-observation runs, on Linux. Steam updates your game for you, and the protocol has to match for you to join.

Is oxide-observation online, and how reliable is it?

oxide-observation is down just now; the last sighting was 42 days 16 hours ago. It was up 0 of 168 hours across the last 7 full days, or 0% of the time. It first appears in Rust Heatmap records on 16 September 2026.

Where is oxide-observation located?

A region is not published for oxide-observation. What Rust Heatmap shows is where a server says it is. Where the machine stands is not looked up. 34.91.74.176:28015 is its address.

Lists and filters

Which Rust Heatmap lists and filters include oxide-observation?

Modded Rust servers, by live population are the Rust Heatmap lists that oxide-observation fits. 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.

What do the server tags on oxide-observation mean?

These are the tags oxide-observation publishes for the game's server browser to read: gmrust (Game mode): Survival in the standard Rust form; mp10 (Max players): Slot count: 10; ts8 (Group limit): At most 8 per team: the default the game ships with; v2633 (Protocol): Your game must match protocol 2633 to get in; cs163794 (Build): This build is 163794; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): The region code is blank; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Listed as Modded, since settings or plugins change the game. Also in the tags, shown at the top of this page: players now, the queue and the time the world was made.

How to join

How do I join oxide-observation?

Press F1 in Rust to open the console, then enter client.connect 34.91.74.176:28015. Alternatively, join from this page with Launch Rust: it opens Rust through Steam and connects you.

KeyServer tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust form.
mp10
Max players Slot count: 10.
ts8
Group limit At most 8 per team: the default the game ships with.
v2633
Protocol Your game must match protocol 2633 to get in.
cs163794
Build This build is 163794.
ptrak
Networking The network layer is RakNet, the game's standard one.
$r?
Region code The region code is blank.

Mods and access

^o
Oxide Oxide (uMod) provides the plugin framework here.
^z
Modded Listed as Modded, since settings or plugins change the 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.