RUST METRICSFlight deck · live data
Data live Servers11,619 Players44,402 Populated2,996 Fresh wipes 3 h128 Scan5 min
‹ All servers163.44.117.113:28015
Offline Full Queue Fresh wipe Wipe due No query

RustServer_28054

Offline 163.44.117.113:28015 checked 22d ago

COM 1 · connect

Server instruments

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

Players now

2% 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,714top 62%
Last wipe28d 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 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 Sep25 Sep30 Sep5 Oct10 Oct15 Oct

Top 62% 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.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 06:38 UTC28d 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_28054?

At their busiest, its recent wipes drew 2 players on average. 1 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does RustServer_28054 follow?

Its rhythm cannot be told from the wipes of RustServer_28054 on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 28 days ago.

Tag meanings

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

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): Slots: 50; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166494 (Build): Game build reading: 166494; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set from RustServer_28054. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show RustServer_28054?

On Rust Metrics, RustServer_28054 sits in these lists: 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.

Player count

What position does RustServer_28054 hold among Rust servers?

Player hours over seven days put RustServer_28054 at #13,714, in the top 62% of all ranked servers.

What is the population on RustServer_28054?

RustServer_28054 is not responding; status offline, last seen 22 days 3 hours ago.

Operator and location

Where does RustServer_28054 sit?

No region tag on RustServer_28054. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 163.44.117.113:28015.

What Rust version is RustServer_28054 on?

Version check: Rust network protocol 2634 and build 166494 on Linux, run by RustServer_28054. To get in, your game needs the same protocol; Steam applies the update.

How reliable is RustServer_28054, and is it online now?

RustServer_28054 reports offline. The last reading came 22 days 3 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 13 September 2026.

Settings and map

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

Reading the name gives no gather rate for RustServer_28054. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

What map is RustServer_28054 on?

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

How to join

How do you connect to RustServer_28054?

Press F1 in Rust and enter client.connect 163.44.117.113: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 mp50,ptrak,$r?,v2634,gmrust,cs166494,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players Slots: 50.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166494
Build Game build reading: 166494.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is 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.