Station XX-14234 · no signal
Pavka
Offline 104.28.196.109:28015 checked 17d ago
- Players now
- 1/ 10
- 10% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #14,234
- top 65%
- Last wipe
- 17d 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 65% 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
- 10.3 daysbetween real wipes
- wipe-day peak
- 1players, 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 |
|---|---|---|---|---|---|---|
| Sun 11 Oct, 21:06 UTC17d ago | M0.0▲rising | 1 | – | – | running | 0 |
| Thu 1 Oct, 13:03 UTC27d ago | – | – | – | – | 10.3 days | 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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer rules
Which map is running on Pavka?
The map on Pavka is procedural, produced by the game.
Which settings and rules apply on Pavka?
You will find no gather rate in the name of Pavka. The group limit is 8 players, the game's default. It plays in survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Oxide. Anti-cheat is on: VAC, from Valve.
Player counts
What is the current population on Pavka?
No players are recorded on Pavka at this moment; it is offline, and the last sighting was 17 days 3 hours ago.
How does Pavka rank against other Rust servers?
Over the last seven days, Pavka recorded enough player hours to reach #14,234 worldwide, placing it in the top 65% of all ranked servers.
Operator and location
How reliably does Pavka stay online?
No contact with Pavka right now, and the last recorded contact was 17 days 3 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. On 27 September 2026 it was recorded for the first time by Rust Server Trends.
Where in the world is Pavka hosted?
Nothing about a region comes from Pavka. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 104.28.196.109:28015.
What build of Rust does Pavka use?
Rust network protocol 2634 and build 167398 on Windows is what Pavka runs. The protocol must match for you to join, and Steam takes care of updating it.
Wipe schedule
What does wipe day look like on Pavka?
1 players, on average, was the busiest crowd at its recent wipes. 0 hours into the latest wipe, the crowd reached its peak.
On what timetable does Pavka run its wipes?
The rhythm of Pavka cannot yet be told: too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 17 days 3 hours.
Lists and tags
What do the server tags on Pavka mean?
The game's server browser reads the tags Pavka publishes: gmrust (Game mode): Survival in standard Rust; mp10 (Max players): 10 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167398 (Build): It runs game build 167398; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. 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 Pavka appear?
You will find Pavka on the following Rust Server Trends lists: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Join the server
What steps get you onto Pavka?
To join, enter client.connect 104.28.196.109:28015 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.
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.