RUST METRICSFlight deck · live data
Data live Servers11,789 Players78,653 Populated3,571 Fresh wipes 3 h243 Scan5 min
‹ All servers160.251.251.72:28015
Offline Full Queue Fresh wipe Wipe due No query

RustServer_26366

Offline 160.251.251.72:28015 checked 17d ago

COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 0.5 1 1.5 2 PAX 0 /2

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,519top 71%
Last wipe18d 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, measured since 4 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k4 Oct7 Oct10 Oct13 Oct16 Oct19 Oct

Top 71% 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 peak2players, last three wipes

The first 48 hours of its last wipes

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 11 Oct, 00:04 UTC18d ago 2 – 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 should you expect from wipe day on RustServer_26366?

The busiest point of its recent wipes drew 2 players on average. Peak crowd on the latest wipe: 0 hours in.

What wipe timing does RustServer_26366 follow?

Its rhythm cannot be told from the wipes of RustServer_26366 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 18 days 22 hours ago.

Tags

Which tags does RustServer_26366 carry, and what do they mean?

These are the tags RustServer_26366 publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp2 (Max players): The server holds 2 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167584 (Build): Build 167584; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does RustServer_26366 appear in Rust Metrics lists and filters?

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

Population

What position does RustServer_26366 hold among Rust servers?

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

What is the population on RustServer_26366?

RustServer_26366 is not responding; status offline, last seen 17 days 8 hours ago.

Server details

Where does RustServer_26366 sit?

Reading: location. RustServer_26366 gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 160.251.251.72:28015.

What Rust version is RustServer_26366 on?

Rust network protocol 2634 and build 167584 on Linux is the build RustServer_26366 runs. Matching protocol is required to join. Let Steam update your game.

What is the uptime on RustServer_26366, and is it online?

RustServer_26366 reports offline. The last reading came 17 days 8 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 4 October 2026, recorded by Rust Metrics.

Settings and map

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

Reading the name gives no gather rate for RustServer_26366. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

What map is RustServer_26366 on?

From seed 1173896606, the game generates the procedural map on RustServer_26366. Its size is 3,750. View it on RustMaps from this page: matching size and seed give an identical map.

Join

What do you do to join RustServer_26366?

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

PLACARDS

Server tags

what each one means

Published as mp2,ptrak,$r?,v2634,gmrust,cs167584,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp2
Max players The server holds 2 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167584
Build Build 167584.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

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.