pepega
Offline 85.193.2.88:28015 checked 29d 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 61% 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- 51/500
- 131/100
- 64/225
- 15/200
- 62/700
- 14/1000
Quick answers
from the figures on this pageWipe schedule
When does pepega wipe?
The rhythm of pepega's wipes cannot be told yet: too few 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 in play was created 47 days 12 hours ago.
Tag meanings
How should you read the tags on pepega?
Tags published by pepega, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp250 (Max players): 250 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): Game build reading: 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does pepega appear in Rust Metrics lists and filters?
These Rust Metrics lists carry pepega: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Population
What position does pepega hold among Rust servers?
Player hours over seven days put pepega at #14,550, in the top 61% of all ranked servers.
How full does pepega get?
pepega is not responding; status offline, last seen 29 days 15 hours ago.
Server details
Which location does pepega run from?
No region tag on pepega. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 85.193.2.88:28015.
What Rust version is pepega on?
Reading: pepega, Rust network protocol 2633 and build 165217, Windows. Matching protocol is required to join. Let Steam update your game.
Is pepega up, and how often does it stay up?
pepega reports offline. The last reading came 29 days 15 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 28 September 2026.
Rules and settings
What settings and rules apply on pepega?
Reading the name gives no gather rate for pepega. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.
Join
How do you connect to pepega?
Check: join. Open Rust, press F1, then enter client.connect 85.193.2.88:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.