RUST METRICSFlight deck · live data
Data live Servers11,888 Players103,803 Populated3,995 Fresh wipes 3 h419 Scan5 min
‹ All servers138.117.194.48:28015
Offline Full Queue Fresh wipe Wipe due No query

Pipoka

Offline 138.117.194.48:28015 checked 6d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 1 /1

Players now

100% full 7-day avg7-day peak
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 1
Rank#13,607top 61%
Last wipe6d agono schedule published
Next wipe–no rhythm it keeps
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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k29 Sep4 Oct10 Oct15 Oct24 Oct29 Oct

Top 61% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

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
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 22 Oct, 21:45 UTC6d ago 1 – running 1
Sat 10 Oct, 17:27 UTC19d 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.

ALTN

Similar servers

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

Quick answers

from the figures on this page

Wipe timing

What happens on Pipoka when wipe day comes?

At their busiest, its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 1 hours in. Until the next wipe, the crowd stayed above half that peak in 100% of its recent wipes.

How often does Pipoka wipe, and when?

There is no next wipe to predict: Pipoka wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 6 days 20 hours ago the current world was made.

Tags

Which tags does Pipoka carry, and what do they mean?

Check: tags. The game's server browser reads gmvanilla (Game mode): The mode is vanilla survival; mp1 (Max players): 1 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set from Pipoka. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does Pipoka appear in Rust Metrics lists and filters?

These Rust Metrics lists carry Pipoka: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.

Population

Where does Pipoka sit in the rankings?

Ranking for Pipoka: #13,607 on seven-day player hours, top 61% of all ranked servers.

What player count does Pipoka carry?

Pipoka is not responding; status offline, last seen 6 days 20 hours ago. Seven-day check: 0 players on average. Peak reading: 1.

Operator and location

Where does Pipoka sit?

No region tag on Pipoka. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 138.117.194.48:28015.

What Rust version is Pipoka on?

Rust network protocol 2635 and build 168909 on Windows is the build Pipoka runs. To get in, your game needs the same protocol; Steam applies the update.

How reliable is Pipoka, and is it online now?

Reading: offline. Pipoka last answered 6 days 20 hours ago. Uptime for the last 7 full days: 2 of 168 hours, or 1%. Reading: first seen 29 September 2026, recorded by Rust Metrics.

Settings and map

How is Pipoka configured, and what rules are in force?

No gather rate appears in the name: Pipoka. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

What map is Pipoka on?

Procedural map on Pipoka, made by the game's generator.

Join

What do you do to join Pipoka?

Press F1 in Rust and enter client.connect 138.117.194.48:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2635,gmvanilla,cs168909,ts8

Game

gmvanilla
Game mode The mode is vanilla survival.
mp1
Max players 1 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build The server runs game build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is 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.