RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h37 Scan5 min
‹ All servers217.116.58.136:28015
Offline Full Queue Fresh wipe Wipe due No query

PISKA

Offline 217.116.58.136:28015 checked 6d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 125 250 375 500 PAX 1 /500

Players now

0% 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 average1peak 2
Rank#10,797top 49%
Last wipe12d agono schedule published
Next wipe–too few wipes seen yet
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
15k10k15k20k5 Oct10 Oct14 Oct19 Oct23 Oct28 Oct

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

PLAN

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 gap6.1 daysbetween real wipes
wipe-day peak2players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Fri 16 OctSat 10 Oct
00.511.52+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 19:05 UTC12d ago 2 – running 2
Sat 10 Oct, 17:52 UTC18d ago 2 held half 6.1 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.

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 PISKA when wipe day comes?

At their busiest, its recent wipes drew 2 players on average. After the latest wipe, numbers topped out at 0 hours. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

What wipe timing does PISKA follow?

To tell the rhythm of PISKA, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 12 days ago.

Lists and filters

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

These are the tags PISKA publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp500 (Max players): 500 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): Game build reading: 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show PISKA?

These Rust Metrics lists carry PISKA: 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 2 weeks.

Population

Where does PISKA sit in the rankings?

Ranking for PISKA: #10,797 on seven-day player hours, top 49% of all ranked servers.

What is the population on PISKA?

Reading for PISKA: offline at this moment; last seen 6 days 23 hours ago. Check: players over seven days. Average 1, peak 2.

Server details

Where does PISKA sit?

No region tag on PISKA. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 217.116.58.136:28015.

What Rust version is PISKA on?

Version check: Rust network protocol 2634 and build 167781 on Windows, run by PISKA. Matching protocol is required to join. Let Steam update your game.

How reliable is PISKA, and is it online now?

Check: connection. PISKA is offline at this moment. Last contact was 6 days 23 hours ago. Uptime for the last 7 full days: 4 of 168 hours, or 2%. Reading: first seen 5 October 2026, recorded by Rust Metrics.

Rules and settings

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

Check: gather rate. The name PISKA does not state one. The group cap is 8 players, which is the default in the game. survival, the normal game: build, gather, raid — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on PISKA?

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

How to join

How do you connect to PISKA?

To join: start Rust, press F1 and type client.connect 217.116.58.136:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp500,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp500
Max players 500 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167781
Build Game build reading: 167781.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.