pablusha_RUST
Offline 5.139.228.240:28015 checked 40d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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 bestWipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 160/250
- 95/200
- 15/250
- 17/250
- 15/100
- 17/200
Quick answers
from the figures on this pageWipe timing
What wipe timing does pablusha_RUST follow?
To tell the rhythm of pablusha_RUST, 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 40 days 11 hours ago.
Tags
How should you read the tags on pablusha_RUST?
Tags published by pablusha_RUST, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp500 (Max players): 500 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs164530 (Build): Game build reading: 164530; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does pablusha_RUST appear in Rust Metrics lists and filters?
These Rust Metrics lists carry pablusha_RUST: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Player count
Where does pablusha_RUST sit in the rankings?
Player hours over seven days put pablusha_RUST at #13,253, in the top – of all ranked servers.
What is the population on pablusha_RUST?
Status for pablusha_RUST: offline. Last seen 40 days 11 hours ago.
Operator and location
Which location does pablusha_RUST run from?
No region comes from pablusha_RUST. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 5.139.228.240:28015.
What Rust version is pablusha_RUST on?
Rust network protocol 2633 and build 164530 on Windows is the build pablusha_RUST runs. Check: protocol. To join, your game must match; Steam handles the update.
What is the uptime on pablusha_RUST, and is it online?
pablusha_RUST reports offline. The last reading came 40 days 11 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 18 September 2026, recorded by Rust Metrics.
Settings and map
How is pablusha_RUST configured, and what rules are in force?
No gather rate appears in the name: pablusha_RUST. The group cap is 8 players, which is the default in the game. Mode check gives survival; gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on pablusha_RUST?
Procedural map on pablusha_RUST, made by the game's generator.
Connection
How can you get onto pablusha_RUST?
Press F1 in Rust and enter client.connect 5.139.228.240:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.