Rust Server TrendsSeismic network · station log
Recording Stations11,706 Players60,014 Active3,275 Wipes · 3 h128 48 h

Station XX-15284 · no signal

Pavel_Smáža

Offline 157.85.87.118:22131 checked 2d ago

vanilla
Connect
Players now
0/ 40
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,284
top 69%
Last wipe
27d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15284 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 40 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct14 Oct22 Oct30 Oct

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

Expected events

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.

wipe-day peak
0players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 2 Oct, 03:03 UTC27d ago M0.0steady 0 – running 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 491 on average
84/ 250
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average
115/ 200
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 284 on average
397/ 450
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 277 on average
21/ 100
Rustoria.co - EU Main EU · groups of 16+ · weekly · 266 on average
476/ 525
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 253 on average
362/ 425
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on Pavel_Smáža?

Generated by the game, the map on Pavel_Smáža is procedural, size 3,000 with seed 1795452926. You can view it on RustMaps from this page: the same size and seed produce the same map.

Which settings and rules apply on Pavel_Smáža?

You will find no gather rate in the name of Pavel_Smáža. At the game's default, groups can have up to 8 players. It plays in survival mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. Under Community in the server browser, it runs as a community server. It describes itself as vanilla, which means no changed rates, kits or rules: this is the game as Facepunch ships it. The server has VAC on, Valve's anti-cheat.

Population

What is the current population on Pavel_Smáža?

Pavel_Smáža is not responding at this moment and is offline, last seen 2 days 6 hours ago. Averaged across the last seven days, the population was 0 players.

How does Pavel_Smáža rank against other Rust servers?

The last seven days of player hours place Pavel_Smáža at #15,284, in the top 69% of all ranked servers.

Server facts

How reliably does Pavel_Smáža stay online?

Pavel_Smáža is down at the moment; the last recorded contact was 2 days 6 hours ago. It was up 69% of the time across the last 7 full days: 116 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.

Which region does Pavel_Smáža run from?

Nothing about a region comes from Pavel_Smáža. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 157.85.87.118:22131.

What build of Rust does Pavel_Smáža use?

On Linux, Pavel_Smáža runs Rust network protocol 2635 and build 168909. The protocol must match for you to join, and Steam takes care of updating it.

Wipe pattern

What does wipe day look like on Pavel_Smáža?

On average, the busiest point of its recent wipes drew 0 players. The peak on the most recent wipe came 0 hours after the wipe.

How often does Pavel_Smáža wipe, and on which days?

The rhythm of Pavel_Smáža cannot yet be told: too few of its wipes are on record. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 27 days 22 hours.

Server tags

What do the server tags on Pavel_Smáža mean?

These are the tags Pavel_Smáža publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp40 (Max players): 40 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^v (Vanilla): No changed rates, kits or rules: this is the game as Facepunch ships it. 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 Pavel_Smáža appear?

The Rust Server Trends lists that take in Pavel_Smáža are: Rust community servers without the side modes and Vanilla Rust servers, recorded live. On the server list, the filters it matches are: Type: Vanilla, Community (not modded, not official) and No plugins at all; Server tag: Vanilla ^v; Group limit: 5 or more.

Join the server

What steps get you onto Pavel_Smáža?

To join, enter client.connect 157.85.87.118:22131 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.

Instrument codes

Server tags

what each one means

Published as mp40,ptrak,$r?,v2635,^v,gmrust,cs168909,ts8

Game

gmrust
Game mode The game mode is standard Rust survival.
mp40
Max players 40 slots are available.
ts8
Group limit Teams max out at 8, the default set by the game.
v2635
Protocol To connect, your game must be on the same protocol, 2635.
cs168909
Build It runs game build 168909.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code A region code has not been set.

Difficulty

^v
Vanilla No changed rates, kits or rules: this is the game as Facepunch ships it.

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.

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.