RUST METRICSFlight deck · live data
Data live Servers11,880 Players96,316 Populated4,103 Fresh wipes 3 h158 Scan5 min
‹ All servers87.225.67.17:28015
Offline Full Queue Fresh wipe Wipe due No query

.

Offline 87.225.67.17:28015 checked 21d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 125 250 375 500 PAX 0 /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#15,955top 71%
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
15k10k15k20k25 Sep29 Sep2 Oct6 Oct9 Oct13 Oct

Top 71% 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.1 daysbetween real wipes
on rhythm38%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, 1 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 5 Oct, 09:51 UTC22d ago 1 – running 0
Sun 4 Oct, 08:49 UTC23d ago 1 – 1 days 1
Sat 3 Oct, 03:32 UTC24d ago 1 – 1.2 days 1
Fri 2 Oct, 11:07 UTC25d ago 1 – 0.7 days 1
Fri 2 Oct, 03:30 UTC25d ago 1 – 0.3 days 0
Wed 30 Sep, 04:29 UTC27d ago 1 – 2 days 1
Tue 29 Sep, 07:15 UTC28d ago 1 – 0.9 days 1
Mon 28 Sep, 00:17 UTC29d ago 1 – 1.3 days 1
Sat 26 Sep, 04:27 UTC31d ago 1 – 1.8 days 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 schedule

What should you expect from wipe day on .?

At their busiest, its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 1 hours.

When does . wipe?

No next wipe can be predicted for ., which wipes at irregular times. 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 22 days 8 hours ago.

Tags

How should you read the tags on .?

These are the tags . publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp500 (Max players): 500 slots in total; ts20 (Group limit): Teams are capped at 20; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166494 (Build): Game build reading: 166494; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $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. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show .?

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

Population

Where does . sit in the rankings?

Ranking for .: #15,955 on seven-day player hours, top 71% of all ranked servers.

What player count does . carry?

Status for .: offline. Last seen 21 days 15 hours ago.

Server details

Where does . sit?

Reading: location. . gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 87.225.67.17:28015.

What Rust version is . on?

Version check: Rust network protocol 2634 and build 166494 on Windows, run by .. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is ., and is it online now?

Check: connection. . is offline at this moment. Last contact was 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 25 September 2026.

Settings and map

What rules does . enforce, and what are its settings?

Check: gather rate. The name . does not state one. The cap on groups is 20 players. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. VAC is on. That is Valve's anti-cheat.

Connection

How can you get onto .?

Press F1 in Rust and enter client.connect 87.225.67.17: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 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 Teams are capped at 20.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166494
Build Game build reading: 166494.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.