RUST METRICSFlight deck · live data
Data live Servers11,831 Players94,092 Populated3,830 Fresh wipes 3 h517 Scan5 min
‹ All servers160.251.254.104:28015
Offline Full Queue Fresh wipe Wipe due No query

RustServer_22377

Offline 160.251.254.104: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#15,996top 71%
Last wipe25d 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 3 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
15k10k15k20k3 Oct5 Oct6 Oct8 Oct9 Oct11 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 peak0players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 4 Oct, 08:12 UTC25d ago 0 – 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_22377?

An average of 0 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

When does RustServer_22377 wipe?

Its rhythm cannot be told from the wipes of RustServer_22377 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 25 days 12 hours ago.

Tags

How should you read the tags on RustServer_22377?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166652 (Build): The server runs game build 166652; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set from RustServer_22377. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does RustServer_22377 appear in Rust Metrics lists and filters?

These Rust Metrics lists carry RustServer_22377: 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.

Population

Where does RustServer_22377 sit in the rankings?

Player hours over seven days put RustServer_22377 at #15,996, in the top 71% of all ranked servers.

What player count does RustServer_22377 carry?

Reading for RustServer_22377: offline at this moment; last seen 25 days 12 hours ago.

Server

Which location does RustServer_22377 run from?

No region comes from RustServer_22377. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 160.251.254.104:28015.

What Rust version is RustServer_22377 on?

Version check: Rust network protocol 2634 and build 166652 on Linux, run by RustServer_22377. Matching protocol is required to join. Let Steam update your game.

Is RustServer_22377 up, and how often does it stay up?

Check: connection. RustServer_22377 is offline at this moment. Last contact was 25 days 12 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 3 October 2026.

Rules and settings

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

Check: gather rate. The name RustServer_22377 does not state one. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

What map is RustServer_22377 on?

Size 3,500 and seed 32607: the game generates the procedural map on RustServer_22377 from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

How to join

What do you do to join RustServer_22377?

Check: join. Open Rust, press F1, then enter client.connect 160.251.254.104: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?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players The server holds 50 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166652
Build The server runs game build 166652.
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.