RUST METRICSFlight deck · live data
Data live Servers11,658 Players32,604 Populated2,794 Fresh wipes 3 h75 Scan5 min
‹ All servers163.44.113.142:28015
Offline Full Queue Fresh wipe Wipe due No query

RustServer_26390

Offline 163.44.113.142:28015 checked 34d 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,424top 60%
Last wipe54d 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 Sep22 Sep24 Sep27 Sep29 Sep1 Oct

Top 60% 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 schedule

How often does RustServer_26390 wipe, and when?

Its rhythm cannot be told from the wipes of RustServer_26390 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 in play was created 54 days 19 hours ago.

Tags

How should you read the tags on RustServer_26390?

These are the tags RustServer_26390 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): Build 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $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_26390 appear in Rust Metrics lists and filters?

On Rust Metrics, RustServer_26390 sits in these lists: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

Where does RustServer_26390 sit in the rankings?

Ranking for RustServer_26390: #13,424 on seven-day player hours, top 60% of all ranked servers.

How full does RustServer_26390 get?

RustServer_26390 is not responding; status offline, last seen 34 days 10 hours ago.

Server details

What location is RustServer_26390 hosted in?

No region tag on RustServer_26390. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 163.44.113.142:28015.

What Rust version is RustServer_26390 on?

Rust network protocol 2633 and build 165217 on Linux is the build RustServer_26390 runs. Matching protocol is required to join. Let Steam update your game.

How reliable is RustServer_26390, and is it online now?

Check: connection. RustServer_26390 is offline at this moment. Last contact was 34 days 10 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.

Rules and settings

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

Reading the name gives no gather rate for RustServer_26390. The group cap is 8 players, which is the default in the game. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. VAC is on. That is Valve's anti-cheat.

Which map is live on RustServer_26390?

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

Connection

What do you do to join RustServer_26390?

Check: join. Open Rust, press F1, then enter client.connect 163.44.113.142: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 Survival, as standard Rust plays it.
mp50
Max players The server holds 50 slots.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Protocol 2633: join only on the same game version.
cs165217
Build Build 165217.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.