RUST METRICSFlight deck · live data
Data live Servers11,704 Players61,057 Populated3,258 Fresh wipes 3 h178 Scan5 min
‹ All servers84.20.17.67:28015
Offline Full Queue Fresh wipe Wipe due No query

#1 MyRustServer

Offline 84.20.17.67:28015 checked 12d 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,240top 70%
Last wipe27d agono schedule published
Next wipe–too few wipes 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
15k10k15k20k6 Oct9 Oct13 Oct17 Oct21 Oct24 Oct

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

PLAN

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.

The first 48 hours of its last wipes

No hourly players around its wipes yet.

Players each hour, from the hour of the wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 8 Oct, 21:52 UTC21d ago – – 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.

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 #1 MyRustServer follow?

Its rhythm cannot be told from the wipes of #1 MyRustServer 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. The world in play was created 27 days 15 hours ago.

Lists and filters

How should you read the tags on #1 MyRustServer?

Check: tags. The game's server browser reads gmvanilla (Game mode): The mode is vanilla survival; mp10 (Max players): Slots: 10; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): The server runs game build 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game from #1 MyRustServer. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does #1 MyRustServer appear in Rust Metrics lists and filters?

On Rust Metrics, #1 MyRustServer sits in these lists: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Occupancy

Where does #1 MyRustServer sit in the rankings?

Ranking for #1 MyRustServer: #15,240 on seven-day player hours, top 70% of all ranked servers.

What is the population on #1 MyRustServer?

#1 MyRustServer is not responding; status offline, last seen 12 days 12 hours ago.

Operator and location

Which location does #1 MyRustServer run from?

No region tag on #1 MyRustServer. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 84.20.17.67:28015.

What Rust version is #1 MyRustServer on?

Rust network protocol 2634 and build 167781 on Windows is the build #1 MyRustServer runs. To get in, your game needs the same protocol; Steam applies the update.

Is #1 MyRustServer up, and how often does it stay up?

#1 MyRustServer reports offline. The last reading came 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 6 October 2026.

Map and rules

How is #1 MyRustServer configured, and what rules are in force?

Check: gather rate. The name #1 MyRustServer does not state one. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

Join

How do you connect to #1 MyRustServer?

Press F1 in Rust and enter client.connect 84.20.17.67: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?,v2634,gmvanilla,cs167781,ts8,^o^z

Game

gmvanilla
Game mode The mode is vanilla survival.
mp10
Max players Slots: 10.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167781
Build The server runs game build 167781.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Check: category. Modded, because plugins or settings alter 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.