StatusLive Servers online11,668 Players48,663 Populated3,138 Wiped · 3 h118 Interval5 min Date29 OCT 2026

DWG RG-S15961Server sheetchecked 22d ago

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

Offline 189.62.151.138:28115 checked 22d ago

2x weekly wipes moddedoxide
Connect
Players now 0/ 10 0% full
7-day average0peak –
Rank#15,961top 71%
Last wipe24d agoweekly schedule
Next wipe3d 14hMon 2 Nov, 00:01 UTC
Fig. 1

Players

No hourly history yet.

Hourly average and peak, UTC.

Fig. 1Players on PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST
Fig. 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.

Fig. 2FPS, entities and memory
Fig. 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.

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

from its schedule tag

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

wipe-day peak1players, last three wipes

Coming wipes

  1. 3d 14hMon 2 Nov, 00:01 UTC
  2. 7d 9hThu 5 Nov, 19:00 UTCFW
  3. 10d 14hMon 9 Nov, 00:01 UTC
  4. 17d 14hMon 16 Nov, 00:01 UTC
  5. 24d 14hMon 23 Nov, 00:01 UTC
  6. 31d 14hMon 30 Nov, 00:01 UTC
  7. 35d 9hThu 3 Dec, 19:00 UTCFW
  8. 38d 14hMon 7 Dec, 00:01 UTC

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
Magic Rust #18 — Vanilla 2x | Baйп 28.10EU · groups of 150+ · 2x · weekly · 332 on average
924 / 970
02
MIRAGE RUST | SUNDAY 2x | VANILLA+ | Wipe 25.10EU · groups of 300+ · 2x · weekly · 314 on average
134 / 1000
03
Magic Rust #14 — Modded 2x (No limit) | PyccкийEU · groups of 300+ · 2x · weekly · 278 on average
205 / 240
04
MIRAGE RUST | MONDAY 2x | VANILLA+ | Wipe 26.10EU · groups of 300+ · 2x · weekly · 275 on average
252 / 1900
05
РОССИЯ X2 / ДЛЯ НОВИЧКОВ / THIS IS RUST!EU · groups of 12+ · 2x · weekly · 218 on average
55 / 100
06
VANILLA x2 | GGRust #4 | Для нoвичкoв 2xEU · groups of 300+ · 2x · weekly · 130 on average
25 / 100
Ref.Similar
General notes

Quick answers

from the figures on this page

Server details

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

Last seen 22 days 4 hours ago; right now PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST is offline. 0 of 168 hours up over the last 7 full days, which is 0% of the time. The first sighting of it by Rust Graphs was on 4 October 2026.

What location is recorded for PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST?

There is no region published by PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. 189.62.151.138:28115 is its address.

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

Rust network protocol 2634 and build 166652 on Linux: that is what PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST runs. Steam updates your game, which must be on the same protocol for you to join.

Counts

How many players are plotted on PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST?

No response from PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST; the server was last seen 22 days 4 hours ago.

In the rankings, which position does PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST hold?

Within the top 71% of all ranked servers: PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST at #15,961 for player hours, seven days recorded.

Schedules

What is recorded on PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST on wipe day?

The recent wipes averaged a busiest count of 1 players. At 0 hours after the latest wipe the crowd was at its peak.

What wipe schedule has been recorded for PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST?

The prediction follows its tag, because too few wipes of PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST are on record to confirm the schedule. On Monday 2 November at 00:01 UTC its next wipe is due. The current world has been in use since 24 days 9 hours ago. A wipe every week is the schedule its tags set out.

Rules and settings

What settings and rules apply on PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST?

The name records 2x gather for PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST. Eight players per group: the default for the game. survival, the standard game: gather, build, raid, is the game mode. Fighting and raiding between players are enabled. The server browser lists it under Modded: plugins or settings change the game. Oxide plugins are run on it. Anti-cheat: VAC, from Valve, is on.

On which map is PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST played?

A procedural map, generated by the game, is what PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST runs.

Tags

On Rust Graphs, which lists and filters contain PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST?

These Rust Graphs lists include PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST: Servers with a 2x gather rate and Modded Rust servers. It is returned by these filters on the server list: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Gather rate: 2x.

On PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST, what is meant by each tag?

gmrust (Game mode): Survival in standard Rust style; mp10 (Max players): The slot count is 10; ts8 (Group limit): The team limit is 8, which is the game default; v2634 (Protocol): To join, your game must be on protocol 2634; cs166652 (Build): 166652 is the game build; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): The region code field is empty; ^w (Weekly): The wipe cycle is one week; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it is listed under Modded are the tags PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST publishes; the game's server browser reads them. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

Connect

How is PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST joined?

Connect with client.connect 189.62.151.138:28115: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you.

NotesAnswered from the figures
Key

Server tags

what each one means

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

Game

gmrust
Game mode Survival in standard Rust style.
mp10
Max players The slot count is 10.
ts8
Group limit The team limit is 8, which is the game default.
v2634
Protocol To join, your game must be on protocol 2634.
cs166652
Build 166652 is the game build.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code The region code field is empty.

Wipe schedule

^w
Weekly The wipe cycle is one week.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Plugins or settings change the game, so it is listed under Modded.

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.

KeyTag string decoded