RUST METRICSFlight deck · live data
Data live Servers11,698 Players65,296 Populated3,536 Fresh wipes 3 h114 Scan5 min
‹ All servers185.185.56.59:28015
Online Full Queue Fresh wipe Wipe due No query

HARD PVE TOP | Classic PvE | RaidBases | Custom Events | No VIP

Online 185.185.56.59:28015 checked 13m ago

biweekly wipes moddedcarbonpvehardcore
COM 1 · connect
Launch Rust and join

Server instruments

last reading Wed 10:00 UTC
0 12 25 38 50 PAX 6 /50

Players now

12% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 190 SERVER FPS

Server fps

48 h low 146 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 118,916 ×1000

Entities

48 h range 100,471–119,297 · memory 3,723 MB
1239 ET SINCE RESTART 06:03

Uptime

6 h 3 min since its last restart, at the last reading
7-day average3peak 11
Rank#3,752top 17%
Last wipe12d agobiweekly schedule
Next wipe1d 4hThu 29 Oct, 16:29 UTC
Memory3,723MB48 h peak 11 players
REC 1

Players
AveragePeak
0510152023:0006:0013:0020:0003:0010:00

Hourly average and peak, UTC.

REC 2

Server performance
010020030040023:0006:0013:0020:0003:0010:00

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 26 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
12k4k6k8k27 Oct28 Oct

Top 17% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

Next wipe Thursday 29 October, 16:29 UTC, in 1d 4h. Biweekly: 14 days after its last 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 HARD PVE TOP | Classic PvE | RaidBases | Custom Events | No VIP wipe, and when?

From biweekly: 14 days after its last wipe, the next wipe of HARD PVE TOP | Classic PvE | RaidBases | Custom Events | No VIP is an estimate. Due on Thursday 29 October at 16:29 UTC is its next wipe. The world in play was created 12 days 19 hours ago. A wipe schedule of every two weeks is published in its tags.

Tag meanings

Which tags does HARD PVE TOP | Classic PvE | RaidBases | Custom Events | No VIP carry, and what do they mean?

Check: tags. The game's server browser reads gmhardcore (Game mode): A harsher set of rules: hardcore; mp50 (Max players): Slots: 50; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^b (Biweekly): Check: wipe cycle. Every two weeks; ^p (PvE): No fighting between players: the world itself is the hazard; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Carbon handles the plugins here from HARD PVE TOP | Classic PvE | RaidBases | Custom Events | No VIP. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does HARD PVE TOP | Classic PvE | RaidBases | Custom Events | No VIP appear in Rust Metrics lists and filters?

These Rust Metrics lists carry HARD PVE TOP | Classic PvE | RaidBases | Custom Events | No VIP: Modded Rust servers, checked live and Rust PvE servers. Reading: server list filters. It comes up under Type: Modded; Game mode: PvE and Hardcore; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.

Player count

What position does HARD PVE TOP | Classic PvE | RaidBases | Custom Events | No VIP hold among Rust servers?

Player hours over seven days put HARD PVE TOP | Classic PvE | RaidBases | Custom Events | No VIP at #3,752, in the top 17% of all ranked servers.

What is the population on HARD PVE TOP | Classic PvE | RaidBases | Custom Events | No VIP?

6 of 50 slots are filled on HARD PVE TOP | Classic PvE | RaidBases | Custom Events | No VIP right now. Seven-day check: 3 players on average. Peak reading: 11. Average at the busiest hour was 10 players, at 18:00 UTC over the last 48 hours.

Server details

What location is HARD PVE TOP | Classic PvE | RaidBases | Custom Events | No VIP hosted in?

No region comes from HARD PVE TOP | Classic PvE | RaidBases | Custom Events | No VIP. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 185.185.56.59:28015.

What Rust version is HARD PVE TOP | Classic PvE | RaidBases | Custom Events | No VIP on?

Rust network protocol 2635 and build 168909 on Linux is the build HARD PVE TOP | Classic PvE | RaidBases | Custom Events | No VIP runs. To get in, your game needs the same protocol; Steam applies the update.

How does HARD PVE TOP | Classic PvE | RaidBases | Custom Events | No VIP perform?

Over the last 48 hours the average was 210 server fps; the floor was 146. Peak entity count: 119,297. Buildings, deployables and all else included. Check: memory. Peak use was 5,100 MB. What players call lag comes from low fps and an entity count on the rise.

Is HARD PVE TOP | Classic PvE | RaidBases | Custom Events | No VIP up, and how often does it stay up?

Check: connection. HARD PVE TOP | Classic PvE | RaidBases | Custom Events | No VIP is online at this moment. Check: restart. The uptime it reports puts the last restart about 6 hours ago. Uptime for the last 1 full day: 24 of 24 hours, or 100%. Check: first contact. Rust Metrics logged it on 26 October 2026.

Rules and settings

What rules does HARD PVE TOP | Classic PvE | RaidBases | Custom Events | No VIP enforce, and what are its settings?

Check: gather rate. The name HARD PVE TOP | Classic PvE | RaidBases | Custom Events | No VIP does not state one. The group cap is 8 players, which is the default in the game. The mode is hardcore. Note the following: Facepunch's most punishing mode. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Carbon plugins are running. Anti-cheat reading: VAC on, Valve's system.

What map is HARD PVE TOP | Classic PvE | RaidBases | Custom Events | No VIP on?

Map: procedural, 4,500, generated by the game, on HARD PVE TOP | Classic PvE | RaidBases | Custom Events | No VIP. Read the map name: Custom Map.

How to join

How can you get onto HARD PVE TOP | Classic PvE | RaidBases | Custom Events | No VIP?

To join: start Rust, press F1 and type client.connect 185.185.56.59: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,^z,^y,^b,^p,gmhardcore,cs168909,ts8

Game

gmhardcore
Game mode A harsher set of rules: hardcore.
mp50
Max players Slots: 50.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

Wipe schedule

^b
Biweekly Check: wipe cycle. Every two weeks.

Gameplay

^p
PvE No fighting between players: the world itself is the hazard.

Mods and access

^z
Modded Check: category. Modded, because plugins or settings alter the game.
^y
Carbon Carbon handles the plugins here.

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.