RUST METRICSFlight deck · live data
Data live Servers11,603 Players34,648 Populated2,845 Fresh wipes 3 h60 Scan5 min
‹ All servers84.85.222.254:28015
Offline Full Queue Fresh wipe Wipe due No query

sus amogmog

Offline 84.85.222.254:28015 checked 2d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 125 250 375 500 PAX 1 /500

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 average1peak 1
Rank#12,826top 58%
Last wipe2d 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
15k10k15k20k25 Oct26 Oct27 Oct28 Oct

Top 58% 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.

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 25 Oct, 13:26 UTC2d ago 1 – 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

Wipe timing

What happens on sus amogmog when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 0 hours.

How often does sus amogmog wipe, and when?

Its rhythm cannot be told from the wipes of sus amogmog 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. The world it runs now was made 2 days 13 hours ago.

Lists and filters

How should you read the tags on sus amogmog?

These are the tags sus amogmog publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp500 (Max players): 500 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Game build reading: 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $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 sus amogmog appear in Rust Metrics lists and filters?

On Rust Metrics, sus amogmog 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 3 days.

Player count

Where does sus amogmog sit in the rankings?

Player hours over seven days put sus amogmog at #12,826, in the top 58% of all ranked servers.

What is the population on sus amogmog?

Status for sus amogmog: offline. Last seen 2 days 13 hours ago. Seven-day check: 1 players on average. Peak reading: 1.

Server

Which location does sus amogmog run from?

Reading: location. sus amogmog gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 84.85.222.254:28015.

What Rust version is sus amogmog on?

Reading: sus amogmog, Rust network protocol 2635 and build 168909, Windows. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on sus amogmog, and is it online?

Check: connection. sus amogmog is offline at this moment. Last contact was 2 days 13 hours ago. Uptime for the last 2 full days: 0 of 48 hours, or 0%. The first sighting on Rust Metrics was 25 October 2026.

Rules and settings

What settings and rules apply on sus amogmog?

No gather rate appears in the name: sus amogmog. The group cap is 8 players, which is the default in the game. Mode check gives survival; gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on sus amogmog?

Check: map. Procedural, generated by the game, on sus amogmog.

Join

What do you do to join sus amogmog?

To join: start Rust, press F1 and type client.connect 84.85.222.254:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp500,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp500
Max players 500 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Game build reading: 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.