RUST METRICSFlight deck · live data
Data live Servers11,826 Players80,135 Populated3,731 Fresh wipes 3 h265 Scan5 min
‹ All servers94.249.148.16:28015
Offline Full Queue Fresh wipe Wipe due No query

Rust Devblog 299 [No-Steam / Oxide]

Offline 94.249.148.16:28015 checked 2d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

Players now

0% full 7-day avg7-day peak
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 1
Rank#14,950top 67%
Last wipe3d 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
15k10k15k20k26 Oct27 Oct28 Oct29 Oct

Top 67% 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

Wipe schedule

How often does Rust Devblog 299 [No-Steam / Oxide] wipe, and when?

Its rhythm cannot be told from the wipes of Rust Devblog 299 [No-Steam / Oxide] on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 3 days 3 hours ago.

Lists and filters

How should you read the tags on Rust Devblog 299 [No-Steam / Oxide]?

These are the tags Rust Devblog 299 [No-Steam / Oxide] publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2594 (Protocol): Your game must run protocol 2594 to get in; cs128111 (Build): Build 128111; ptrak (Networking): Network layer: RakNet, the standard for the game; $reu2 (Region code): Region code reading: eu2; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Plugins or settings make this a modded server. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show Rust Devblog 299 [No-Steam / Oxide]?

On Rust Metrics, Rust Devblog 299 [No-Steam / Oxide] sits in these lists: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

Occupancy

Where does Rust Devblog 299 [No-Steam / Oxide] sit in the rankings?

Ranking for Rust Devblog 299 [No-Steam / Oxide]: #14,950 on seven-day player hours, top 67% of all ranked servers.

How full does Rust Devblog 299 [No-Steam / Oxide] get?

Rust Devblog 299 [No-Steam / Oxide] is not responding; status offline, last seen 2 days 14 hours ago. Check: players over seven days. Average 0, peak 1.

Operator and location

Where does Rust Devblog 299 [No-Steam / Oxide] sit?

No region comes from Rust Devblog 299 [No-Steam / Oxide], and its region code is eu2. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 94.249.148.16:28015.

What Rust version is Rust Devblog 299 [No-Steam / Oxide] on?

Reading: Rust Devblog 299 [No-Steam / Oxide], Rust network protocol 2594 and build 128111, Windows. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is Rust Devblog 299 [No-Steam / Oxide], and is it online now?

Rust Devblog 299 [No-Steam / Oxide] reports offline. The last reading came 2 days 14 hours ago. Reading: 2% uptime over the last 2 full days. It was up 1 of 48 hours. Reading: first seen 26 October 2026, recorded by Rust Metrics.

Rules and settings

What settings and rules apply on Rust Devblog 299 [No-Steam / Oxide]?

Check: gather rate. The name Rust Devblog 299 [No-Steam / Oxide] does not state one. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Oxide of them. VAC is off. That is Valve's anti-cheat.

What map is Rust Devblog 299 [No-Steam / Oxide] on?

Procedural map on Rust Devblog 299 [No-Steam / Oxide], made by the game's generator.

Join

What do you do to join Rust Devblog 299 [No-Steam / Oxide]?

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

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$reu2,v2594,gmrust,cs128111,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players 50 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2594
Protocol Your game must run protocol 2594 to get in.
cs128111
Build Build 128111.
ptrak
Networking Network layer: RakNet, the standard for the game.
$reu2
Region code Region code reading: eu2.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Plugins or settings make this a modded server.

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.