RUST METRICSFlight deck · live data
Data live Servers11,697 Players44,561 Populated3,120 Fresh wipes 3 h101 Scan5 min
‹ All servers201.235.233.251:28015
Offline Full Queue Fresh wipe Wipe due No query

Pibeland: Segundo Acto II

Offline 201.235.233.251:28015 checked 10d ago

moddedcarbon
COM 1 · connect

Server instruments

no direct query in 48 hours
0 4 8 11 15 PAX 0 /15

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,316top 70%
Last wipe12d 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 15 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
15k10k15k20k15 Oct17 Oct19 Oct21 Oct23 Oct25 Oct

Top 70% 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.

usual gap0.9 daysbetween real wipes
wipe-day peak3players, last three wipes

The first 48 hours of its last wipes

Fri 16 OctThu 15 Oct
00.511.52+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 17:01 UTC12d ago 3 – running 2
Thu 15 Oct, 19:24 UTC13d ago 3 – 0.9 days 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

Reset cycle

What should you expect from wipe day on Pibeland: Segundo Acto II?

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

What wipe timing does Pibeland: Segundo Acto II follow?

The rhythm of Pibeland: Segundo Acto II's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 12 days 2 hours ago the current world was made.

Tags

How should you read the tags on Pibeland: Segundo Acto II?

Check: tags. The game's server browser reads gmvanilla (Game mode): Check: mode. Vanilla survival; mp15 (Max players): The server holds 15 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): Game build reading: 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Carbon handles the plugins here from Pibeland: Segundo Acto II. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does Pibeland: Segundo Acto II appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Pibeland: Segundo Acto II: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Player count

Where does Pibeland: Segundo Acto II sit in the rankings?

Player hours over seven days put Pibeland: Segundo Acto II at #15,316, in the top 70% of all ranked servers.

How full does Pibeland: Segundo Acto II get?

Pibeland: Segundo Acto II is not responding; status offline, last seen 10 days 13 hours ago.

Server details

What location is Pibeland: Segundo Acto II hosted in?

Reading: location. Pibeland: Segundo Acto II gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 201.235.233.251:28015.

What Rust version is Pibeland: Segundo Acto II on?

Reading: Pibeland: Segundo Acto II, Rust network protocol 2634 and build 167781, Windows. To get in, your game needs the same protocol; Steam applies the update.

Is Pibeland: Segundo Acto II up, and how often does it stay up?

Reading: offline. Pibeland: Segundo Acto II last answered 10 days 13 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 15 October 2026.

Map and rules

What settings and rules apply on Pibeland: Segundo Acto II?

Check: gather rate. The name Pibeland: Segundo Acto II does not state one. 8 players per group, the default value. survival, the normal game: build, gather, raid — that is the game mode. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Plugin count: Carbon. Check: anti-cheat. VAC, Valve's system, is on.

What map is Pibeland: Segundo Acto II on?

From seed 1281909505, the game generates the procedural map on Pibeland: Segundo Acto II. Its size is 3,500. View it on RustMaps from this page: matching size and seed give an identical map.

Connection

How do you connect to Pibeland: Segundo Acto II?

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

PLACARDS

Server tags

what each one means

Published as mp15,ptrak,$r?,v2634,gmvanilla,cs167781,ts8,^z,^y

Game

gmvanilla
Game mode Check: mode. Vanilla survival.
mp15
Max players The server holds 15 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167781
Build Game build reading: 167781.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

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.