Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO T SRV11,721online PAX48,587playing OCC3,224with players WIPED 3H110
MODModded traffic
Callsign

PCU1225↓

PUCA |HUN| OFFICIAL

Online 51.178.187.59:28080 checked 8m ago

moddedoxide
Clearance · join
Players now 3/ 100 3% full
7-day average13peak 46
Rank#1,225top 6%
Last wipe2d agono schedule published
Next wipe7d 18hThu 5 Nov, 19:00 UTC FW
Track history

Players

AveragePeak
02040608001:0010:0019:0003:0012:0022:00

Hourly average and peak, UTC.

Server performance

05010015020001:0010:0019:0003:0012:0022: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.

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.

Flight plan

Wipe schedule

a steady gap
ETD · next wipe

Next wipe Thursday 5 November, 19:00 UTC, in 7d 18h.

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. 7d 18hThu 5 Nov, 19:00 UTCFW
  2. 17d 23hSun 15 Nov, 23:37 UTC
  3. 28d 6hThu 26 Nov, 06:35 UTC
  4. 35d 18hThu 3 Dec, 19:00 UTCFW
  5. 38d 13hSun 6 Dec, 13:32 UTC

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.

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.

Nearby traffic

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. 01MOD
    Callsign SHC102no group limit · 156 on average ShockRust | Blue | NoLimit
    Players 46/500
  2. 02MOD
    Callsign STR581EU · groups of 8+ · weekly · 128 on average МИНИ-КАРТА 2Х | STORM | FPS+ 28.10
    Players 127/100
  3. 03MOD
    Callsign RTR811EU · groups of 16+ · weekly · 117 on average RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10
    Players 44/225
  4. 04MOD
    Callsign RUS021EU · groups of 16+ · monthly · 92 on average 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10
    Players 42/700
  5. 05MOD
    Callsign RST016EU · groups of 12+ · weekly · 88 on average RustSpain.com | EU Main
    Players 7/200
  6. 06MOD
    Callsign RUS021EU · groups of 16+ · monthly · 84 on average 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10
    Players 5/1000
ATIS · this server

Quick answers

From the figures on this page.

Filters

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

Modded servers, tracked live — the Rust Tracker lists that include PUCA |HUN| OFFICIAL. It comes up under these filters 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.

What do the tags mean that PUCA |HUN| OFFICIAL is listed under?

The game's server browser reads these tags from PUCA |HUN| OFFICIAL: gmrust (Game mode): Survival as standard Rust plays; mp100 (Max players): 100 slots on this server; ts8 (Group limit): Teams cap at 8; this is the game default; v2635 (Protocol): Your game must be on protocol 2635 to connect; cs168909 (Build): Build: 168909; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): Region code: not set; ^o (Oxide): A plugin framework runs here: Oxide (uMod); ^z (Modded): Under Modded: the game is changed by plugins or settings. Current players, queue length and world creation time sit in the tags as well, shown at the top of this page.

Wipe Schedule

What happens on PUCA |HUN| OFFICIAL on wipe day?

At their busiest, recent wipes averaged 35 players. The peak on the latest wipe came 33 hours after it. Half the peak was held until the next wipe in 67% of its recent wipes. The fall below half came by day 1 where it did not hold.

Which wipe times are confirmed for PUCA |HUN| OFFICIAL?

The recent gap between wipes at PUCA |HUN| OFFICIAL is about 10.3 days. On Thursday 5 November at 19:00 UTC the force wipe lands, its next wipe, and every Rust server wipes with it. This world has been running 2 days 14 hours.

Location and Status

Is PUCA |HUN| OFFICIAL up, and how does its uptime hold?

Tracking shows PUCA |HUN| OFFICIAL online as of now. About 16 hours ago it restarted last, based on reported uptime. 59 of 168 hours up over the last 7 full days: 35% uptime. First contact for Rust Tracker: 24 September 2026.

Which Rust build is PUCA |HUN| OFFICIAL running?

Rust network protocol 2635 and build 168909 is the build on PUCA |HUN| OFFICIAL; the platform is Windows. Steam updates it for you; your game must share the protocol to join.

Is PUCA |HUN| OFFICIAL holding performance?

For the last 48 hours it averaged 108 server fps; the floor was 71. Buildings, deployables and the rest of the world took it to a maximum of 88,322 entities. It drew as much as 2,896 MB of memory. Players feel lag when fps drops and the entity count climbs.

What location is PUCA |HUN| OFFICIAL hosted in?

Region: none published by PUCA |HUN| OFFICIAL. The location shown by Rust Tracker is the server's own claim; no lookup of the machine's position is made. Connect on 51.178.187.59:28080.

Population

How many players are on PUCA |HUN| OFFICIAL right now?

PUCA |HUN| OFFICIAL is at 3 players, capacity 100. Peak of 46 in the last seven days, average 13 players. At 18:00 UTC it drew its highest average of the last 48 hours: 42 players.

How does PUCA |HUN| OFFICIAL compare in the rankings?

Top 6% of all ranked servers, and #1,225 on seven-day player hours: PUCA |HUN| OFFICIAL.

Settings

Which settings and rules are confirmed on PUCA |HUN| OFFICIAL?

Nothing in PUCA |HUN| OFFICIAL's name states a gather rate. The game's default applies: groups can have up to 8 players. It runs survival, gather, build, raid, as the game intends. Fighting and raiding between players are on. Plugins or settings change the game, and the server browser lists it under Modded. Oxide plugins run on it. On: VAC, Valve's anti-cheat.

Which map is confirmed for PUCA |HUN| OFFICIAL?

A procedural map of size 3,500 runs on PUCA |HUN| OFFICIAL, generated by the game from seed 1862422565. Same size, same seed, same map. RustMaps shows it, linked from this page.

Connect

What is the way to join PUCA |HUN| OFFICIAL?

Open the console in Rust with F1 after starting the game, then type client.connect 51.178.187.59:28080. Alternatively, Launch Rust here opens Rust via Steam and connects you.

Transponder codes

Server tags

What each one means.

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

Game

gmrust
Game mode Survival as standard Rust plays.
mp100
Max players 100 slots on this server.
ts8
Group limit Teams cap at 8; this is the game default.
v2635
Protocol Your game must be on protocol 2635 to connect.
cs168909
Build Build: 168909.
ptrak
Networking Network layer: RakNet, the game's standard.
$r?
Region code Region code: not set.

Mods and access

^o
Oxide A plugin framework runs here: Oxide (uMod).
^z
Modded Under Modded: the game is changed by plugins or settings.

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.