Station XX-14149 · no signal
Pavka
Offline 95.54.230.81:28015 checked 37d ago
- Players now
- 1/ 10
- 10% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #14,149
- top 62%
- Last wipe
- 37d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 10 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 62% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 2.9 daysbetween real wipes
- wipe-day peak
- 2players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Tue 22 Sep, 10:33 UTC37d ago | M0.0■steady | 1 | – | – | running | 1 |
| Sat 19 Sep, 13:34 UTC40d ago | M0.0▲rising | 2 | – | 2.9 days | 1 |
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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageRules and settings
Which map is running on Pavka?
Pavka uses a procedural map, which the game generates.
Which settings and rules apply on Pavka?
The name of Pavka gives no gather rate. The group limit is 8 players, the game's default. It plays in survival mode, gather, build and raid in the standard game. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.
Player counts
How many players are recorded on Pavka right now?
No players are recorded on Pavka at this moment; it is offline, and the last sighting was 37 days 16 hours ago.
How does Pavka rank against other Rust servers?
On player hours for the past week, Pavka sits at #14,149, which puts it inside the top 62% of every ranked server.
Operator and location
How reliably does Pavka stay online?
As recorded now, Pavka is not reachable, the last contact having been 37 days 16 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. 19 September 2026 is when Rust Server Trends first recorded it.
Which region does Pavka run from?
A region is not published by Pavka. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 95.54.230.81:28015.
Which Rust version is Pavka running?
Pavka is running Rust network protocol 2633 and build 164530 on a machine with Windows. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
What does wipe day look like on Pavka?
2 players, on average, was the busiest crowd at its recent wipes. 0 hours after the latest wipe, the crowd peaked.
On what timetable does Pavka run its wipes?
Too few wipes of Pavka are on record yet to show its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The present world dates from 37 days 16 hours.
Tags
What do the server tags on Pavka mean?
These are the tags Pavka publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp10 (Max players): Slots: 10; ts8 (Group limit): Teams max out at 8, the default set by the game; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs164530 (Build): Game build: 164530; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does Pavka appear?
You will find Pavka on the following Rust Server Trends lists: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Connecting
How do you connect to Pavka?
Enter client.connect 95.54.230.81:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
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.