Working its way up from the back of the class: #15,316 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
15/ 100
F
Lost ground: down 10,673 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); momentum is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 best
RankRank in region
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···WW··
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
Players each hour, from the hour of the wipe. The latest peaked at 3, 3 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 16 Oct, 17:01 UTC11d ago
3
–
running
2
Thu 15 Oct, 19:24 UTC12d 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Which region is Pibeland: Segundo Acto II based in?
You'll find no region listed by Pibeland: Segundo Acto II. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 201.235.233.251:28015.
Is Pibeland: Segundo Acto II up, and how steady is its uptime?
You cannot join now: Pibeland: Segundo Acto II is offline, last seen 9 days 21 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 15 October 2026.
On what Rust version does Pibeland: Segundo Acto II sit?
The server Pibeland: Segundo Acto II is on Rust network protocol 2634 and build 167781 under Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
When does Pibeland: Segundo Acto II wipe, and how often?
There are too few wipes on record for Pibeland: Segundo Acto II to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 11 days 10 hours.
What happens on Pibeland: Segundo Acto II when wipe day arrives?
Across its recent wipes, the busiest moments averaged 3 players. The crowd on the latest wipe was largest 3 hours after it began.
Population
Where does Pibeland: Segundo Acto II sit among Rust servers?
In the top 70% of all ranked servers, Pibeland: Segundo Acto II sits at #15,316 for player hours over the last seven days.
What does the population on Pibeland: Segundo Acto II look like?
The last sighting of Pibeland: Segundo Acto II was 9 days 21 hours ago, and it is offline right now.
Tags and filters
How should you read the tags on Pibeland: Segundo Acto II?
gmvanilla (Game mode): You play vanilla survival here; mp15 (Max players): Its slot count is 15; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): Carbon provides the plugin framework here are the tags Pibeland: Segundo Acto II publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature Pibeland: Segundo Acto II?
These Rust Server Score lists count Pibeland: Segundo Acto II among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Server rules
Which rules does Pibeland: Segundo Acto II enforce, and what are its settings?
The name of Pibeland: Segundo Acto II gives no gather rate. With no change from the game default, groups take up to 8 players. survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Carbon plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Pibeland: Segundo Acto II runs which map?
A procedural map of size 3,500 and seed 1281909505, generated by the game, is what Pibeland: Segundo Acto II runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
What is the way to join Pibeland: Segundo Acto II?
Enter client.connect 201.235.233.251:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp15,ptrak,$r?,v2634,gmvanilla,cs167781,ts8,^z,^y
Game
gmvanilla
Game modeYou play vanilla survival here.
mp15
Max playersIts slot count is 15.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
^y
CarbonCarbon provides the plugin framework 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.
A term to build on. Strongest in standing (F); momentum is the one to work on (F).