RUST METRICSFlight deck · live data
Data live Servers11,803 Players69,659 Populated3,689 Fresh wipes 3 h123 Scan5 min
‹ All servers45.144.52.87:28015
Offline Full Queue Fresh wipe Wipe due No query

.

Offline 45.144.52.87:28015 checked 21d ago

moddedoxide
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 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#13,772top 61%
Last wipe22d agono schedule published
Next wipe–no rhythm it keeps
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 Sep25 Sep29 Sep4 Oct8 Oct13 Oct

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

PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap1 daysbetween real wipes
on rhythm50%of its recent wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Mon 5 OctSun 4 OctSat 3 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 5 Oct, 09:51 UTC22d ago 1 – running 0
Sun 4 Oct, 08:37 UTC23d ago 1 – 1.1 days 0
Sat 3 Oct, 03:32 UTC24d ago 1 – 1.2 days 0
Wed 30 Sep, 04:29 UTC27d ago 0 – 3 days 0
Tue 29 Sep, 07:15 UTC28d ago 1 – 0.9 days 0
Mon 28 Sep, 06:42 UTC29d ago 1 – 1 days 1
Mon 28 Sep, 00:17 UTC29d ago 1 – 0.3 days 1
Sat 26 Sep, 04:27 UTC31d ago 1 – 1.8 days 1
Fri 25 Sep, 06:57 UTC32d ago 1 – 0.9 days 1
Tue 22 Sep, 03:26 UTC35d ago 1 held half 3.1 days 1

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

What happens on . when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. 6 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does . follow?

There is no next wipe to predict: . wipes at irregular times. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 22 days 12 hours ago the current world was made.

Tags

How should you read the tags on .?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp500 (Max players): 500 slots in total; ts20 (Group limit): Team cap: 20; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166494 (Build): Build 166494; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Plugins or settings make this a modded server from .. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does . appear in Rust Metrics lists and filters?

Rust Metrics lists featuring .: 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.

Occupancy

What position does . hold among Rust servers?

Ranking for .: #13,772 on seven-day player hours, top 61% of all ranked servers.

What player count does . carry?

Reading for .: offline at this moment; last seen 21 days 15 hours ago.

Operator and location

Which location does . run from?

No region tag on .. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 45.144.52.87:28015.

What Rust version is . on?

Reading: ., Rust network protocol 2634 and build 166494, Windows. To get in, your game needs the same protocol; Steam applies the update.

How reliable is ., and is it online now?

. reports offline. The last reading came 21 days 15 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 13 September 2026.

Rules and settings

How is . configured, and what rules are in force?

Reading the name gives no gather rate for .. Check: group limit. Up to 20 players. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.

How to join

How do you connect to .?

To join: start Rust, press F1 and type client.connect 45.144.52.87: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?,v2634,gmrust,cs166494,ts20,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp500
Max players 500 slots in total.
ts20
Group limit Team cap: 20.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166494
Build Build 166494.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^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.