RUST METRICSFlight deck · live data
Data live Servers11,765 Players59,281 Populated3,483 Fresh wipes 3 h134 Scan5 min
‹ All servers51.178.187.59:28080
Online Full Queue Fresh wipe Wipe due No query

PUCA |HUN| OFFICIAL

Online 51.178.187.59:28080 checked 6m ago

moddedoxide
COM 1 · connect

Server instruments

last reading Wed 21:00 UTC
0 25 50 75 100 PAX 8 /100

Players now

8% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 79 SERVER FPS

Server fps

48 h low 71 · below 20 is lag, below 10 is bad
0 25 50 75 100 ENT 88,128 ×1000

Entities

48 h range 64,029–88,322 · memory 2,509 MB
1239 ET SINCE RESTART 15:52

Uptime

15 h 52 min since its last restart, at the last reading
7-day average13peak 46
Rank#1,223top 6%
Last wipe2d agono schedule published
Next wipe7d 20hThu 5 Nov, 19:00 UTC FW
Memory2,509MB48 h peak 46 players
REC 1

Players

AveragePeak
02040608023:0008:0017:0002:0011:0021:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020023:0008:0017:0002:0011:0021: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 24 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
15k10k15k20k24 Sep1 Oct8 Oct14 Oct21 Oct28 Oct

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

PLAN

Wipe schedule

a steady gap

Next wipe Thursday 5 November, 19:00 UTC, in 7d 20h. The force wipe · high confidence

usual gap10.3 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak35players, last three wipes
crowd held67%else halves by day 1

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC7d 20hFW
  2. WPT 2Sun 15 Nov, 23:37 UTC18d 0h
  3. WPT 3Thu 26 Nov, 06:35 UTC28d 7h
  4. WPT 4Thu 3 Dec, 19:00 UTC35d 20hFW
  5. WPT 5Sun 6 Dec, 13:32 UTC38d 14h

The first 48 hours of its last wipes

Mon 26 OctWed 14 OctMon 5 Oct
020406080+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 26 Oct, 09:43 UTC2d ago 46 – running 8
Wed 14 Oct, 17:43 UTC14d ago 50+9 queue held half 11.7 days 37
Mon 5 Oct, 17:35 UTC23d ago 10 held half 9 days 0
Fri 25 Sep, 10:38 UTC33d ago 2 halved by day 1 10.3 days 1

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 PUCA |HUN| OFFICIAL?

At their busiest, its recent wipes drew 35 players on average. After the latest wipe, numbers topped out at 33 hours. The crowd stayed above half that peak until the next wipe in 67% of its recent wipes. By day 1 it fell below half when it didn't.

How often does PUCA |HUN| OFFICIAL wipe, and when?

The recent wipe interval on PUCA |HUN| OFFICIAL is about 10.3 days. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. 2 days 12 hours ago the current world was made.

Tags

How should you read the tags on PUCA |HUN| OFFICIAL?

Tags published by PUCA |HUN| OFFICIAL, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): 100 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show PUCA |HUN| OFFICIAL?

On Rust Metrics, PUCA |HUN| OFFICIAL sits in these lists: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days; Average players: 10+ on average.

Population

Where does PUCA |HUN| OFFICIAL sit in the rankings?

Ranking for PUCA |HUN| OFFICIAL: #1,223 on seven-day player hours, top 6% of all ranked servers.

What player count does PUCA |HUN| OFFICIAL carry?

Current headcount on PUCA |HUN| OFFICIAL: 8 players, 100 slots available. Seven-day check: 13 players on average. Peak reading: 46. Average at the busiest hour was 42 players, at 18:00 UTC over the last 48 hours.

Operator and location

Which location does PUCA |HUN| OFFICIAL run from?

No region comes from PUCA |HUN| OFFICIAL. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 51.178.187.59:28080.

What Rust version is PUCA |HUN| OFFICIAL on?

Reading: PUCA |HUN| OFFICIAL, Rust network protocol 2635 and build 168909, Windows. Matching protocol is required to join. Let Steam update your game.

How does PUCA |HUN| OFFICIAL perform?

Check: fps. Average 108 server fps over the last 48 hours, low of 71. Within range. Peak entity count: 88,322. Buildings, deployables and all else included. Reading: 2,896 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.

How reliable is PUCA |HUN| OFFICIAL, and is it online now?

PUCA |HUN| OFFICIAL reports online. Status: normal. Reading: uptime. About 15 hours ago it restarted, on its own count. Uptime for the last 7 full days: 83 of 168 hours, or 49%. Reading: first seen 24 September 2026, recorded by Rust Metrics.

Map and rules

What rules does PUCA |HUN| OFFICIAL enforce, and what are its settings?

Check: gather rate. The name PUCA |HUN| OFFICIAL does not state one. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on PUCA |HUN| OFFICIAL?

Check: map. Procedural, size 3,500, seed 1862422565, generated by the game on PUCA |HUN| OFFICIAL. View it on RustMaps from this page: matching size and seed give an identical map.

Join

How do you connect to PUCA |HUN| OFFICIAL?

Press F1 in Rust and enter client.connect 51.178.187.59:28080. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp100
Max players 100 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build The server runs game build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Modded: plugins or settings depart from the stock game.

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.