pepega
Offline 85.193.2.170:28015 checked 27d 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 bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe 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- 205/500
- 121/100
- 183/225
- 126/700
- 19/200
- 50/1000
Quick answers
from the figures on this pageWipe timing
What wipe timing does pepega follow?
To tell the rhythm of pepega, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 48 days 6 hours ago.
Tag meanings
How should you read the tags on pepega?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp250 (Max players): Slots: 250; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): Game build reading: 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Plugins or settings make this a modded server from pepega. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show pepega?
These Rust Metrics lists carry pepega: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Occupancy
Where does pepega sit in the rankings?
Ranking for pepega: #16,275 on seven-day player hours, top 69% of all ranked servers.
What is the population on pepega?
pepega is not responding; status offline, last seen 27 days ago.
Server
What location is pepega hosted in?
Reading: location. pepega gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 85.193.2.170:28015.
What Rust version is pepega on?
Version check: Rust network protocol 2633 and build 165217 on Windows, run by pepega. To get in, your game needs the same protocol; Steam applies the update.
How reliable is pepega, and is it online now?
Reading: offline. pepega last answered 27 days ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 1 October 2026.
Settings and map
What settings and rules apply on pepega?
Reading the name gives no gather rate for pepega. 8 players per group, the default value. survival, the normal game: build, gather, raid — that is the game mode. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Oxide plugins are running. VAC is on. That is Valve's anti-cheat.
Join
How can you get onto pepega?
Press F1 in Rust and enter client.connect 85.193.2.170:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.