RUST METRICSFlight deck · live data
Data live Servers11,855 Players81,723 Populated3,800 Fresh wipes 3 h365 Scan5 min
‹ All servers163.44.123.109:28015
Offline Full Queue Fresh wipe Wipe due No query

RustServer_528

Offline 163.44.123.109:28015 checked 27d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

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#16,019top 69%
Last wipe48d agono schedule published
Next wipe–no wipe 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 17 Sep. 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 Sep24 Sep27 Sep1 Oct4 Oct8 Oct

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

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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

When does RustServer_528 wipe?

Its rhythm cannot be told from the wipes of RustServer_528 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. 48 days 17 hours ago the current world was made.

Tag meanings

How should you read the tags on RustServer_528?

These are the tags RustServer_528 publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): Game build reading: 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does RustServer_528 appear in Rust Metrics lists and filters?

These Rust Metrics lists carry RustServer_528: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

What position does RustServer_528 hold among Rust servers?

Player hours over seven days put RustServer_528 at #16,019, in the top 69% of all ranked servers.

What player count does RustServer_528 carry?

RustServer_528 is not responding; status offline, last seen 27 days 17 hours ago.

Server details

Which location does RustServer_528 run from?

Reading: location. RustServer_528 gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 163.44.123.109:28015.

What Rust version is RustServer_528 on?

Rust network protocol 2633 and build 165217 on Linux is the build RustServer_528 runs. To get in, your game needs the same protocol; Steam applies the update.

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

Check: connection. RustServer_528 is offline at this moment. Last contact was 27 days 17 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 RustServer_528 configured, and what rules are in force?

Reading the name gives no gather rate for RustServer_528. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

What map is RustServer_528 on?

From seed 22978, the game generates the procedural map on RustServer_528. Its size is 3,000. The map repeats when size and seed match. Open it on RustMaps from this page.

Connection

How do you connect to RustServer_528?

Check: join. Open Rust, press F1, then enter client.connect 163.44.123.109:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players 50 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Match the game version: protocol 2633 is required.
cs165217
Build Game build reading: 165217.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none 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.