RUST METRICSFlight deck · live data
Data live Servers11,878 Players98,796 Populated3,935 Fresh wipes 3 h404 Scan5 min
‹ All servers160.251.255.52:28015
Offline Full Queue Fresh wipe Wipe due No query

RustServer_577

Offline 160.251.255.52:28015 checked 22d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 0 /1

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,983top 71%
Last wipe26d 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 2 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
15k10k15k20k2 Oct4 Oct6 Oct9 Oct11 Oct13 Oct

Top 71% 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

Reset cycle

What wipe timing does RustServer_577 follow?

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

Lists and filters

How should you read the tags on RustServer_577?

Tags published by RustServer_577, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): Slots: 1; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166586 (Build): Game build reading: 166586; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show RustServer_577?

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

Population

What position does RustServer_577 hold among Rust servers?

Ranking for RustServer_577: #15,983 on seven-day player hours, top 71% of all ranked servers.

What player count does RustServer_577 carry?

Reading for RustServer_577: offline at this moment; last seen 22 days 20 hours ago.

Server details

Where does RustServer_577 sit?

No region tag on RustServer_577. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 160.251.255.52:28015.

What Rust version is RustServer_577 on?

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

How reliable is RustServer_577, and is it online now?

Check: connection. RustServer_577 is offline at this moment. Last contact was 22 days 20 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 2 October 2026.

Settings and map

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

Reading the name gives no gather rate for RustServer_577. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on RustServer_577?

Size 4,250 and seed 1636364137: the game generates the procedural map on RustServer_577 from them. The map repeats when size and seed match. Open it on RustMaps from this page.

How to join

What do you do to join RustServer_577?

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

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2634,gmrust,cs166586,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players Slots: 1.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166586
Build Game build reading: 166586.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.