Station XX-15316 · no signal
Pibeland: Segundo Acto II
Offline 201.235.233.251:28015 checked 9d ago
- Players now
- 0/ 15
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,316
- top 70%
- Last wipe
- 11d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 15 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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.
Rank
daily · 1 is bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 0.9 daysbetween real wipes
- wipe-day peak
- 3players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 3 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Fri 16 Oct, 17:01 UTC11d ago | M0.0▲rising | 3 | – | running | 2 | |
| Thu 15 Oct, 19:24 UTC12d ago | M0.5▲rising | 3 | – | 0.9 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer rules
Which map is running on Pibeland: Segundo Acto II?
Generated by the game, the map on Pibeland: Segundo Acto II is procedural, size 3,500 with seed 1281909505. From this page you can look at it on RustMaps, since the same size and seed give the same map.
Which settings and rules apply on Pibeland: Segundo Acto II?
No gather rate appears in the name of Pibeland: Segundo Acto II. Groups hold up to 8 players, which is the default for the game. survival is the game mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. Carbon is the plugin framework it runs. Anti-cheat is on: VAC, from Valve.
Player counts
How many players are recorded on Pibeland: Segundo Acto II right now?
Pibeland: Segundo Acto II is not responding at this moment and is offline, last seen 9 days 12 hours ago.
How does Pibeland: Segundo Acto II rank against other Rust servers?
Over the last seven days, Pibeland: Segundo Acto II recorded enough player hours to reach #15,316 worldwide, placing it in the top 70% of all ranked servers.
Operator and location
How reliably does Pibeland: Segundo Acto II stay online?
No contact with Pibeland: Segundo Acto II right now, and the last recorded contact was 9 days 12 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 15 October 2026 is when Rust Server Trends first recorded it.
Which region does Pibeland: Segundo Acto II run from?
A region is not published by Pibeland: Segundo Acto II. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 201.235.233.251:28015.
What build of Rust does Pibeland: Segundo Acto II use?
Rust network protocol 2634 and build 167781 on Windows is what Pibeland: Segundo Acto II runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
What does wipe day look like on Pibeland: Segundo Acto II?
On average, the busiest point of its recent wipes drew 3 players. 3 hours into the latest wipe, the crowd reached its peak.
On what timetable does Pibeland: Segundo Acto II run its wipes?
Too few wipes of Pibeland: Segundo Acto II are on record yet to show its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 11 days 1 hours.
Tags
What do the server tags on Pibeland: Segundo Acto II mean?
These are the tags Pibeland: Segundo Acto II publishes for the browser to read: gmvanilla (Game mode): Survival in vanilla mode; mp15 (Max players): 15 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167781 (Build): It runs game build 167781; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): A plugin framework, Carbon, runs here. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does Pibeland: Segundo Acto II appear?
The Rust Server Trends lists that take in Pibeland: Segundo Acto II are: Modded Rust servers, tracked live. You will find it under these filters 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.
How to join
How do you connect to Pibeland: Segundo Acto II?
To join, enter client.connect 201.235.233.251:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.