RUST METRICSFlight deck · live data
Data live Servers11,814 Players74,934 Populated3,774 Fresh wipes 3 h146 Scan5 min
‹ All servers85.193.2.231:28015
Offline Full Queue Fresh wipe Wipe due No query

pepega

Offline 85.193.2.231:28015 checked 28d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 62 125 188 250 PAX 1 /250

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#14,543top 61%
Last wipe51d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k29 Sep30 Sep2 Oct3 Oct5 Oct6 Oct

Top 61% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What wipe timing does pepega follow?

Its rhythm cannot be told from the wipes of pepega on record: there are too few. 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 51 days 15 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): The server holds 250 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): The server runs game build 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show pepega?

These Rust Metrics lists carry pepega: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Occupancy

What position does pepega hold among Rust servers?

Player hours over seven days put pepega at #14,543, in the top 61% of all ranked servers.

What is the population on pepega?

pepega is not responding; status offline, last seen 28 days 10 hours ago.

Server details

What location is pepega hosted in?

Reading: location. pepega gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 85.193.2.231: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.

Is pepega up, and how often does it stay up?

pepega reports offline. The last reading came 28 days 10 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 29 September 2026, recorded by Rust Metrics.

Rules and settings

What settings and rules apply on pepega?

No gather rate appears in the name: pepega. 8 players per group, the default value. survival, the normal game: build, gather, raid — that is the game mode. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on pepega?

The game generates a procedural map for pepega.

Join

How do you connect to pepega?

Check: join. Open Rust, press F1, then enter client.connect 85.193.2.231:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp250,ptrak,$r?,v2633,gmrust,cs165217,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp250
Max players The server holds 250 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build The server runs game build 165217.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Check: category. Modded, because plugins or settings alter the game.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.