Rust Data

rustdata.spaceservers157.157.78.137:28017.ipynb

Run all rust-data · live

‹ All servers

Online 157.157.78.137:28015 checked 10m ago

Rozpierducha PL [Solo|2x]

2x solo moddedoxide

Connect

srv = rust.server("157.157.78.137:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/100 # 0% full
7-day average 0 # peak 1
rank #12,355 # top 56%
last wipe 24d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75114:0023:0008:0017:0003:0012:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020014:0023:0008:0017:0003:0012:00

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, measured since 3 Oct. 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
15k10k15k20k3 Oct8 Oct13 Oct19 Oct24 Oct29 Oct

Top 56% of all ranked servers, and #189 of the solo servers (top 85%). Ranked on player hours over the last seven days.

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

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

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+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 Sun 4 Oct, 17:06 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

3500 · seed 1337
Map of Rozpierducha PL [Solo|2x]
map
Procedural Map
size
3500
seed
1337
Open on RustMaps

Server

srv.info()
address
157.157.78.137:28015
region
–
max players
100
group limit
solo
wipe schedule
–
last wipe
4 Oct 2026, 17:06 UTC
hostname
–
first seen
3 Oct 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0WARBANDITS.GG EU 2X SOLO ONLY|Loot+|X2 JUST WIPEDEU · solo · 2x · weekly · 64 on average36/200
1Blood Rust - Purple [solo, x2]EU · solo · 2x · weekly · 54 on average49/200
2Magic Rust #16 — Modded 2x (Toлькo SOLO) | PyccкийEU · solo · 2x · weekly · 43 on average51/100
3EU RENEGADE 2x Monthly | SOLO ONLY | 50% Upkeep | No BP Wipe |EU · solo · 2x · monthly · 39 on average21/150
4DOPERUST.COM – 2X EU Solo Only – 50% Upkeep|Noob FriendlyEU · solo · 2x · monthly · 32 on average32/100
5EU Limitless 2x Solo Only | No BP Wipes|Noob Friendly|x2|Max 1EU · solo · 2x · weekly · 29 on average9/200

Quick answers

From the figures on this page.

Population

What position does Rozpierducha PL [Solo|2x] take in the server rankings?

Over the last seven days Rozpierducha PL [Solo|2x] sits at #12,355 on player hours, in the top 56% of ranked servers. The solo group places it at #189.

What population does Rozpierducha PL [Solo|2x] carry?

Rozpierducha PL [Solo|2x] reports 0 players at this refresh, with 100 slots configured. Over the last seven days it averaged 0 players and peaked at 1. Peak hour in the last 48 hours: 23:00 UTC, mean 1 players.

Server facts

How well does Rozpierducha PL [Solo|2x] perform?

Averaged over 48 hours: 117 server fps, never under 101. The entity count peaked at 66,267, covering buildings, deployables and the rest of the world. The memory field tops out at 3,044 MB. Low fps plus an entity count on the way up is the lag players report.

What Rust version does Rozpierducha PL [Solo|2x] run?

The build is Rust network protocol 2635 and build 168909 on Linux, run by Rozpierducha PL [Solo|2x]. Steam updates your game for you, but the protocol must match to join.

Is Rozpierducha PL [Solo|2x] up, and what does its uptime show?

Rozpierducha PL [Solo|2x] reports itself online at the current refresh. Count back 3 days 21 hours from its reported uptime to get the last restart. Over the last 7 full days the hours up number 167 of 168, 99%. The first row Rust Data holds for it is dated 3 October 2026.

Which location does Rozpierducha PL [Solo|2x] run from?

Its name points to Europe, but Rozpierducha PL [Solo|2x] publishes no region tag. 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 157.157.78.137:28015.

Map and rules

Which rules apply on Rozpierducha PL [Solo|2x], and what settings?

Gather sits at 2x, read from the server's own name: Rozpierducha PL [Solo|2x]. Solo play only. Teams are not allowed. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.

What is the map on Rozpierducha PL [Solo|2x]?

Size 3,500, seed 1337: the procedural map on Rozpierducha PL [Solo|2x], generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipes and dates

When does Rozpierducha PL [Solo|2x] wipe, and on what schedule?

A rhythm cannot be read from the wipes of Rozpierducha PL [Solo|2x] on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 24 days 20 hours ago.

On Rozpierducha PL [Solo|2x], what happens on wipe day?

Recent wipes averaged 1 players at their peak. The crowd on the latest wipe topped out 0 hours after it began.

Tags and filters

Where does Rozpierducha PL [Solo|2x] appear among Rust Data lists and filters?

These Rust Data lists include Rozpierducha PL [Solo|2x]: EU Rust servers, Modded Rust servers, 2x Rust servers and Solo Rust servers, group limit 1. Under these filters on the server list, it is listed: Region: Europe; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Solo; Gather rate: 2x.

How should you read the server tags on Rozpierducha PL [Solo|2x]?

These tags are published by Rozpierducha PL [Solo|2x] and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): The server lists 100 slots; ts1 (Group limit): The team cap is 1; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Join steps

How can I connect to Rozpierducha PL [Solo|2x]?

In Rust, F1 opens the console: type client.connect 157.157.78.137:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp100,ptrak,$r?,v2635,gmrust,cs168909,ts1,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp100
Max players The server lists 100 slots.
ts1
Group limit The team cap is 1.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Build number: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is set.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it sits 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.

Rust Data 72,372 players 11,823 servers online