RUST METRICSFlight deck · live data
Data live Servers11,878 Players98,796 Populated3,935 Fresh wipes 3 h404 Scan5 min
‹ All servers189.62.151.138:28115
Offline Full Queue Fresh wipe Wipe due No query

PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST

Offline 189.62.151.138:28115 checked 22d ago

2x weekly wipes moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

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#15,961top 71%
Last wipe24d agoweekly schedule
Next wipe3d 7hMon 2 Nov, 00:01 UTC
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
15k10k15k20k5 Oct7 Oct9 Oct10 Oct12 Oct14 Oct

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

PLAN

Wipe schedule

from its schedule tag

Next wipe Monday 2 November, 00:01 UTC, in 3d 7h. Its weekly schedule tag · low confidence

wipe-day peak1players, last three wipes

Coming wipes

  1. WPT 1Mon 2 Nov, 00:01 UTC3d 7h
  2. WPT 2Thu 5 Nov, 19:00 UTC7d 2hFW
  3. WPT 3Mon 9 Nov, 00:01 UTC10d 7h
  4. WPT 4Mon 16 Nov, 00:01 UTC17d 7h
  5. WPT 5Mon 23 Nov, 00:01 UTC24d 7h
  6. WPT 6Mon 30 Nov, 00:01 UTC31d 7h
  7. WPT 7Thu 3 Dec, 19:00 UTC35d 2hFW
  8. WPT 8Mon 7 Dec, 00:01 UTC38d 7h

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 5 Oct, 00:01 UTC24d ago 1 – running 0

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

Wipe timing

What happens on PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST when wipe day comes?

The busiest point of its recent wipes drew 1 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST follow?

The prediction follows its tag, because too few of PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST's wipes are on record to confirm its schedule. Due on Monday 2 November at 00:01 UTC is its next wipe. 24 days 16 hours ago the current world was made. Its tags carry a weekly wipe schedule.

Lists and filters

Which tags does PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST carry, and what do they mean?

These are the tags PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166652 (Build): The server runs game build 166652; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^w (Weekly): Check: wipe cycle. Every week; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST appear in Rust Metrics lists and filters?

These Rust Metrics lists carry PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST: 2x Rust servers, checked live and Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Gather rate: 2x.

Occupancy

Where does PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST sit in the rankings?

Player hours over seven days put PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST at #15,961, in the top 71% of all ranked servers.

What is the population on PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST?

Reading for PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST: offline at this moment; last seen 22 days 12 hours ago.

Operator and location

What location is PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST hosted in?

Reading: location. PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 189.62.151.138:28115.

What Rust version is PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST on?

Reading: PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST, Rust network protocol 2634 and build 166652, Linux. Matching protocol is required to join. Let Steam update your game.

How reliable is PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST, and is it online now?

Reading: offline. PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST last answered 22 days 12 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 4 October 2026.

Rules and settings

How is PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST configured, and what rules are in force?

The name carries the rate: 2x gather on PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST. No limit is set beyond the default. Groups take up to 8 players. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Oxide of them. VAC is on. That is Valve's anti-cheat.

Which map is live on PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST?

The game generates a procedural map for PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST.

Connection

What do you do to join PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST?

To join: start Rust, press F1 and type client.connect 189.62.151.138:28115. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,^w,gmrust,cs166652,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players 10 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166652
Build The server runs game build 166652.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

Wipe schedule

^w
Weekly Check: wipe cycle. Every week.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Modded: plugins or settings depart from the stock 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.