RUST METRICSFlight deck · live data
Data live Servers11,615 Players38,895 Populated2,943 Fresh wipes 3 h85 Scan5 min
‹ All servers163.44.119.1:28015
Offline Full Queue Fresh wipe Wipe due No query

RustServer_8625

Offline 163.44.119.1:28015 checked 25d 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,006top 70%
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 Sep28 Sep2 Oct6 Oct10 Oct

Top 70% 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_8625 wipe?

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

Tag meanings

How should you read the tags on RustServer_8625?

These are the tags RustServer_8625 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): 50 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): Build 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does RustServer_8625 appear in Rust Metrics lists and filters?

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

Player count

What position does RustServer_8625 hold among Rust servers?

Ranking for RustServer_8625: #16,006 on seven-day player hours, top 70% of all ranked servers.

What is the population on RustServer_8625?

Reading for RustServer_8625: offline at this moment; last seen 25 days 20 hours ago.

Operator and location

Where does RustServer_8625 sit?

Reading: location. RustServer_8625 gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 163.44.119.1:28015.

What Rust version is RustServer_8625 on?

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

How reliable is RustServer_8625, and is it online now?

RustServer_8625 reports offline. The last reading came 25 days 20 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

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

No gather rate appears in the name: RustServer_8625. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

Which map is live on RustServer_8625?

Check: map. Procedural, size 3,000, seed 23127, generated by the game on RustServer_8625. The map repeats when size and seed match. Open it on RustMaps from this page.

Join

How can you get onto RustServer_8625?

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

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players 50 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build Build 165217.
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.