Skip to main content

Independent statistics on public Rust serversNot affiliated with Facepunch Studios

Latest count: 56,681 players on 11,752 servers
Rust CensusThe census of every public Rust server, counted and refreshed.

Statistical profileOffline

Pibeland: Segundo Acto II

201.235.233.251:28015 checked 10d ago

moddedcarbon
Release date
Next release
In five minutes (11:40 UTC)
Source
Live server queries
Server address
201.235.233.251:28015
First recorded
15 October 2026

Connect to this server

Launch Rust and join

1. Main points

Players now

0/ 15

0% full

7-day average

0

peak –

Rank

#15,316

top 70%

Last wipe

12d ago

no schedule published

Next wipe

–

too few wipes seen yet

Main points

  • The server is offline; at its last check there were 0 players on it, 0% of its 15 slots.
  • It ranks #15,316 of all ranked servers, the top 70%, on player hours over the last seven days.
  • Its current map went up 12d ago.

2. Players

Figure 1: Players on Pibeland: Segundo Acto II

Players now and over time, UTC

No hourly history yet.

Hourly average and peak, UTC.

Source: Live server queries, Rust Census

3. Server performance

Figure 2: Frame rate, entities and memory

From asking the server directly; low fps and a climbing entity count mean lag

This server has not answered a direct query in the last 48 hours.

Note

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.

4. Rank

Figure 3: Rank among all servers, 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.

Source: Live server queries, Rust Census

5. Wipe schedule

Patterntoo 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 gap

0.9 days

between real wipes

Wipe-day peak

3

players, last three wipes

Figure 4: The first 48 hours of its last wipes

Players each hour, from the hour of the wipe

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.

Source: Live server queries, Rust Census

6. Wipes

Table 1: Wipes, newest first

Every wipe seen on this server

WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 17:01 UTC12d ago 3 – running 2
Thu 15 Oct, 19:24 UTC13d ago 3 – 0.9 days 0

Notes

  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.
  2. A new world less than six hours after a wipe is a restart, not a wipe of its own.

Source: Live server queries, Rust Census

7. Map

Figure 5: Map of Pibeland: Segundo Acto II

3500 · seed 1281909505

Map of Pibeland: Segundo Acto II

Table 2: The world

As the server publishes it

MapProcedural Map
Size3500
Seed1281909505
Open on RustMaps

8. Server characteristics

Table 3: Characteristics of Pibeland: Segundo Acto II

What the server publishes and what was recorded

Address201.235.233.251:28015
Region–
Max players15
Group limit8, the default
Wipe schedule–
Last wipe16 Oct 2026, 22:37 UTC
Hostname–
First seen15 Oct 2026

9. About this server

In its own words: the description the server publishes, unedited.

PIBELAND — ACTO 2: EL LEGADO DE LA GUERRA Todo comenzó en el Acto 0. Mausito, Leo, Toma, Mauri, Nico y Requete llegaron a una isla donde sobrevivir significaba construir, conquistar y estar dispuesto a pelear por cada recurso. Las primeras bases se convirtieron en fortalezas. Las disputas terminaron en guerras y las alianzas comenzaron a quebrarse. Entre todos, Mausito era el más poderoso: controlaba territorios, acumulaba armas y su nombre imponía respeto en toda la isla. Requete murió durante los conflictos del Acto 0. Pero la mayor batalla de aquella etapa llegaría cuando los habitantes restantes dejaron de lado sus diferencias y se unieron para enfrentar a Mausito. Prepararon un raideo conjunto contra su fortaleza, decididos a terminar con su dominio. Las explosiones abrieron sus muros y el fuego consumió la base. Entre los disparos, el humo y los derrumbes, perdieron de vista a Mausito. Cuando terminó el ataque, solo quedaron escombros. Mausito fue declarado muerto. Se creyó que había quedado sepultado entre las ruinas, pero nadie encontró su cuerpo. Nadie pudo confirmar haberlo visto morir. Desde aquella noche, no se supo nada más de él. Leo, Toma, Mauri y Nico sobrevivieron. Mientras luchaban por ocupar el lugar que Mausito había dejado, algo extraño ocurrió frente a la costa. Una noche llegaron barcos sin luces. Unos hombres desconocidos bajaron de ellos con cuatro prisioneros: Tome, Ense, Risso y Escarcha. Los llevaron a distintos lugares de la isla y los abandonaron desnudos, sin comida, sin herramientas y sin decirles por qué estaban allí. C

10. Similar servers

Table 4: Servers like this one

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

ServerCharacteristicsPlayers
ShockRust | Blue | NoLimitno group limit · 157 on average61 / 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average134 / 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 117 on average61 / 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 92 on average51 / 700
RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average16 / 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average9 / 1000

11. Quick answers

From the figures on this page.

Wipe details

This release records the wipe timetable for Pibeland: Segundo Acto II: what is it?

Too few wipes of Pibeland: Segundo Acto II are on record to establish its rhythm. A force wipe takes place monthly for every Rust server, with the next on Thursday 5 November at 19:00 UTC. 12 days have passed since this world was made.

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

An average of 3 players attended at peak across recent wipes. On the latest wipe, 3 hours passed before the crowd peaked.

About the server

How reliable is Pibeland: Segundo Acto II, and is it online now?

Pibeland: Segundo Acto II is offline at the time of this release; it was last seen 10 days 11 hours ago. Of the 168 hours in the last 7 full days, it was up 0 of them, or 0%. It was first seen by Rust Census on 15 October 2026.

Which location does Pibeland: Segundo Acto II run from?

No region is published by Pibeland: Segundo Acto II. Rust Census does not look up where the machine stands; it shows where a server says it is. At 201.235.233.251:28015 it is addressed.

On which Rust version does Pibeland: Segundo Acto II operate?

Rust network protocol 2634 and build 167781 on Windows is the version Pibeland: Segundo Acto II runs. The same protocol is required for your game to join, and Steam updates it for you.

Player figures

What are the current player figures for Pibeland: Segundo Acto II?

The last count for Pibeland: Segundo Acto II was 10 days 11 hours ago; it is offline at present.

In the rankings of Rust servers, where is Pibeland: Segundo Acto II placed?

The rank for Pibeland: Segundo Acto II is #15,316 on seven-day player hours, in the top 70% of ranked servers.

Lists and tags

Where does Pibeland: Segundo Acto II appear among the Rust Census lists and filters?

These Rust Census lists include Pibeland: Segundo Acto II: Modded Rust servers, counted. Under these filters it comes up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Which meanings do the tags on Pibeland: Segundo Acto II carry?

gmvanilla (Game mode): The mode is vanilla survival; mp15 (Max players): 15 slots are available; ts8 (Group limit): Teams are capped at 8, the default the game ships with; v2634 (Protocol): To connect, your game version must match protocol 2634; cs167781 (Build): The server runs game build 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^z (Modded): Modded: the game is changed by plugins or settings; ^y (Carbon): Carbon, a plugin framework, is installed are the tags Pibeland: Segundo Acto II publishes, and the game's server browser reads them. At the top of this page you will find the tags for current players, queue and world creation time.

Map and rules

Which map has been recorded for Pibeland: Segundo Acto II?

The procedural map on Pibeland: Segundo Acto II is generated by the game, measures 3,500 and carries seed 1281909505. Because one size and seed give one map, RustMaps can display it from this page.

What settings and rules have been listed for Pibeland: Segundo Acto II?

No gather rate is recorded for Pibeland: Segundo Acto II in its name. The group cap stands at 8 players, the default for the game. survival is the game mode recorded, the standard game: gather, build, raid. Raiding and player combat are permitted. Modded is its section in the server browser, because plugins or settings change the game. The plugin count is Carbon. VAC, Valve's anti-cheat, is enabled.

Join details

How can you connect to Pibeland: Segundo Acto II?

Enter client.connect 201.235.233.251:28015 in the console, opened with F1 after starting Rust; alternatively, Launch Rust on this page opens Rust through Steam and connects you.

12. Server tags

What each tag this server publishes means: a glossary.

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

Game

gmvanillaGame mode The mode is vanilla survival.
mp15Max players 15 slots are available.
ts8Group limit Teams are capped at 8, the default the game ships with.
v2634Protocol To connect, your game version must match protocol 2634.
cs167781Build The server runs game build 167781.
ptrakNetworking The network layer is RakNet, the game's standard.
$r?Region code A region code has not been set.

Mods and access

^zModded Modded: the game is changed by plugins or settings.
^yCarbon Carbon, a plugin framework, is installed.

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.