On the class lists: C+ (65), with population over 48 hours and no performance mark.
Players now1/ 1100% full
7-day average0peak 1
Rank#13,643top 61%
Last wipe6d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
44/ 100
F
Room for more players: 0 of 1 on average.
Standingrank on player hours
39/ 100
F
Working its way up from the back of the class: #13,643 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
100/ 100
A+
Holds its players well after a wipe: 100% of wipes kept half their crowd.
Momentumrank now against a week ago
55/ 100
C−
Moving up: up 1,482 places this week.
A fair term, with more to come.
Strongest in wipe hold (A+); standing 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.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 61% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·W·····
·····W·
·······
···W···
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap11.5 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Thu 22 OctSat 10 OctTue 29 Sep
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 22 Oct, 21:45 UTC6d ago
1
–
running
1
Sat 10 Oct, 17:27 UTC18d ago
1
–
12.2 days
1
Tue 29 Sep, 23:00 UTC29d ago
1
✓ held half
10.8 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
You'll find no region listed by Pipoka. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 138.117.194.48:28015.
Is Pipoka up, and how steady is its uptime?
You cannot join now: Pipoka is offline, last seen 6 days 16 hours ago. For the last 7 full days, it was up 2 of 168 hours, or 1% of the time. It was first seen by Rust Server Score on 29 September 2026.
What Rust version is Pipoka on?
Rust network protocol 2635 and build 168909 on Windows is what Pipoka runs. Steam updates your game for you, but you need the same protocol to join.
Resets
How frequently does Pipoka wipe its map?
There is no next wipe to predict on Pipoka, as it wipes at irregular times. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 6 days 17 hours.
What should you expect from wipe day on Pipoka?
Recent wipes have peaked at 1 players on average. Peak numbers came 1 hours into the latest wipe. The crowd stayed above half that peak, right through to the next wipe, in 100% of its recent wipes.
Player count
What position does Pipoka hold in the rankings?
Over the last seven days, Pipoka has #13,643 for player hours, in the top 61% of all ranked servers.
Is Pipoka a busy server?
It has been 6 days 16 hours since Pipoka was last seen, and it is offline right now. Averaging 0 players over seven days, it peaked at 1.
Lists and filters
How should you read the tags on Pipoka?
The game's browser takes its cue from the tags Pipoka has set: gmvanilla (Game mode): You play vanilla survival here; mp1 (Max players): Its slot count is 1; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does Pipoka appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Pipoka among them: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.
Rules and settings
How is Pipoka set up, and what rules does it keep?
You will find no gather rate in the name of Pipoka. The group limit stays at the game's default of 8 players. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it under Community, as a community server. The server runs Valve's anti-cheat, VAC.
Pipoka runs which map?
The game generates a procedural map for Pipoka.
Getting in
What is the way to join Pipoka?
To connect, start Rust, press F1, and type client.connect 138.117.194.48:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp1,ptrak,$r?,v2635,gmvanilla,cs168909,ts8
Game
gmvanilla
Game modeYou play vanilla survival here.
mp1
Max playersIts slot count is 1.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
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 fair term, with more to come. Strongest in wipe hold (A+); standing is the one to work on (F).