Rust Data

rustdata.spaceservers189.62.151.138:28117.ipynb

Run all rust-data · live

‹ All servers

Offline 189.62.151.138:28115 checked 22d ago

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

2x weekly wipes moddedoxide

Connect

srv = rust.server("189.62.151.138:28117")
print(srv.connect_command)

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak –
rank #15,961 # top 71%
last wipe 24d ago # weekly schedule
next wipe 3d 8h # Mon 2 Nov, 00:01 UTC

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 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.

Wipe schedule · from its schedule tag

srv.wipe_schedule()

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

wipe-day peak1players, last three wipes

Coming wipes

inatkind
03d 8hMon 2 Nov, 00:01 UTCwipe
17d 3hThu 5 Nov, 19:00 UTCFW force wipe
210d 8hMon 9 Nov, 00:01 UTCwipe
317d 8hMon 16 Nov, 00:01 UTCwipe
424d 8hMon 23 Nov, 00:01 UTCwipe
531d 8hMon 30 Nov, 00:01 UTCwipe
635d 3hThu 3 Dec, 19:00 UTCFW force wipe
738d 8hMon 7 Dec, 00:01 UTCwipe

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.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Mon 5 Oct, 00:01 UTC24d ago 1 NaN 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.

display(srv.map, srv.info())

Map

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
189.62.151.138:28115
region
–
max players
10
group limit
8, the default
wipe schedule
weekly
last wipe
5 Oct 2026, 00:01 UTC
hostname
–
first seen
4 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Magic Rust #18 — Vanilla 2x | Baйп 28.10EU · groups of 150+ · 2x · weekly · 333 on average911/1060
1MIRAGE RUST | SUNDAY 2x | VANILLA+ | Wipe 25.10EU · groups of 300+ · 2x · weekly · 317 on average154/1000
2Magic Rust #14 — Modded 2x (No limit) | PyccкийEU · groups of 300+ · 2x · weekly · 283 on average223/300
3MIRAGE RUST | MONDAY 2x | VANILLA+ | Wipe 26.10EU · groups of 300+ · 2x · weekly · 281 on average277/1900
4РОССИЯ / КЛАССИКА X2 / THIS IS RUST!EU · groups of 12+ · 2x · weekly · 218 on average54/100
5VANILLA x2 | GGRust #4 | Для нoвичкoв 2xEU · groups of 300+ · 2x · weekly · 130 on average27/100

Quick answers

From the figures on this page.

Population

What position does PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST take in the server rankings?

Over the last seven days PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST sits at #15,961 on player hours, in the top 71% of ranked servers.

What population does PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST carry?

PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST returns no live count at this refresh, having last been seen 22 days 10 hours ago.

Server facts

What Rust version does PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST run?

Rust network protocol 2634 and build 166652 on Linux is what PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST runs. The protocol has to match before you can join, and Steam does the updating.

Is PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST up, and what does its uptime show?

PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST is offline at this refresh; the last response came 22 days 10 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 4 October 2026.

Which location does PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST run from?

There is no region published for PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 189.62.151.138:28115.

Map and rules

What rules and settings are recorded for PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST?

Gather sits at 2x, read from the server's own name: PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST. The group limit sits at the default of 8 players. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. Anti-cheat status: VAC on.

Which map has PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST selected?

The game generates its map: procedural, on PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST.

Wipe schedule

On what schedule does PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST wipe?

The prediction follows the tag, because PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST's wipes on record are too few to confirm the schedule. Monday 2 November at 00:01 UTC is when the next wipe is due. A new world was started 24 days 15 hours ago, and that is the one in play. The tags list wipes as weekly.

On PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST, what happens on wipe day?

The average peak over recent wipes is 1 players. 0 hours after the latest wipe, the crowd reached its peak.

Tags, lists

Which lists on Rust Data hold PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST, and which filters?

On Rust Data, PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST appears in these lists: Modded Rust servers and 2x Rust servers. These filters bring it up 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.

How should you read the server tags on PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST?

These tags are published by PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166652 (Build): The server runs build 166652; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^w (Weekly): A wipe every week; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

How to join

What is the way to join PEPEL | CORE 2x | TRIO | WEEKLY | LOCAL TEST?

Enter client.connect 189.62.151.138:28115 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players 10 slots in total.
ts8
Group limit Team limit of 8, as shipped by default.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs166652
Build The server runs build 166652.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code Region code: not set.

Wipe schedule

^w
Weekly A wipe every week.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded Modded listing: the game is changed by plugins or settings.

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.

Rust Data 93,384 players 11,848 servers online