pepega
Offline 85.193.2.20: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- 150/500
- 123/100
- 181/225
- 91/700
- 5/200
- 40/1000
Quick answers
from the figures on this pageReset cycle
What wipe timing does pepega follow?
Its rhythm cannot be told from the wipes of pepega on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 47 days 21 hours ago the current world was made.
Tag meanings
How should you read the tags on pepega?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp250 (Max players): Slots: 250; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163493 (Build): The server runs game build 163493; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game from pepega. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show pepega?
On Rust Metrics, pepega sits in these lists: 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.
Player count
What position does pepega hold among Rust servers?
Player hours over seven days put pepega at #14,458, in the top – of all ranked servers.
How full does pepega get?
Reading for pepega: offline at this moment; last seen 40 days 17 hours ago.
Operator and location
Where does pepega sit?
No region comes from pepega. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 85.193.2.20:28015.
What Rust version is pepega on?
Rust network protocol 2633 and build 163493 on Windows is the build pepega runs. To get in, your game needs the same protocol; Steam applies the update.
What is the uptime on pepega, and is it online?
Check: connection. pepega is offline at this moment. Last contact was 40 days 17 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 17 September 2026.
Map and rules
What rules does pepega enforce, and what are its settings?
Check: gather rate. The name pepega does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.
Join
How can you get onto pepega?
Press F1 in Rust and enter client.connect 85.193.2.20:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.