RUST METRICSFlight deck · live data
Data live Servers11,842 Players74,292 Populated3,699 Fresh wipes 3 h224 Scan5 min
‹ All servers160.251.174.60:28015
Offline Full Queue Fresh wipe Wipe due No query

RustServer_570

Offline 160.251.174.60:28015 checked 5d ago

COM 1 · connect
Launch Rust and join

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,326top 69%
Last wipe26d 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 22 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
15k10k15k20k22 Sep29 Sep7 Oct14 Oct22 Oct29 Oct

Top 69% 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 peak5players, last three wipes

The first 48 hours of its last wipes

02468+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 13:03 UTC27d ago 5 – 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

Wipe schedule

What should you expect from wipe day on RustServer_570?

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

When does RustServer_570 wipe?

To tell the rhythm of RustServer_570, too few of its wipes are on record. 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 26 days 22 hours ago.

Tags

How should you read the tags on RustServer_570?

Tags published by RustServer_570, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Game build reading: 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does RustServer_570 appear in Rust Metrics lists and filters?

Rust Metrics lists featuring RustServer_570: 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_570 sit in the rankings?

Player hours over seven days put RustServer_570 at #15,326, in the top 69% of all ranked servers.

How full does RustServer_570 get?

Reading for RustServer_570: offline at this moment; last seen 5 days 16 hours ago. A seven-day average of 0 players is the reading.

Operator and location

What location is RustServer_570 hosted in?

Reading: location. RustServer_570 gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 160.251.174.60:28015.

What Rust version is RustServer_570 on?

Rust network protocol 2635 and build 168909 on Linux is the build RustServer_570 runs. Matching protocol is required to join. Let Steam update your game.

How reliable is RustServer_570, and is it online now?

Check: connection. RustServer_570 is offline at this moment. Last contact was 5 days 16 hours ago. Uptime for the last 7 full days: 46 of 168 hours, or 27%. The first sighting on Rust Metrics was 22 September 2026.

Rules and settings

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

Check: gather rate. The name RustServer_570 does not state one. The group cap is 8 players, which is the default in the game. 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. Check: anti-cheat. VAC, Valve's system, is on.

What map is RustServer_570 on?

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

Connection

How can you get onto RustServer_570?

To join: start Rust, press F1 and type client.connect 160.251.174.60: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?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players 50 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Game build reading: 168909.
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.