RUST METRICSFlight deck · live data
Data live Servers11,830 Players81,821 Populated3,745 Fresh wipes 3 h270 Scan5 min
‹ All servers157.157.78.137:28015
Online Full Queue Fresh wipe Wipe due No query

Rozpierducha PL [Solo|2x]

Online 157.157.78.137:28015 checked 14m ago

2x solo moddedoxide
COM 1 · connect

Server instruments

last reading Thu 13:00 UTC
0 25 50 75 100 PAX 0 /100

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 126 SERVER FPS

Server fps

48 h low 101 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 65,475 ×1000

Entities

48 h range 63,441–66,267 · memory 2,669 MB
1239 ET SINCE RESTART 3D 22H

Uptime

3 days 22 hours since its last restart, at the last reading
7-day average0peak 1
Rank#12,352top 55%
Last wipe24d agono schedule published
Next wipe–too few wipes seen yet
Memory2,669MB48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75115:0000:0009:0019:0004:0013:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020015:0000:0009:0019:0004:0013: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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k3 Oct8 Oct13 Oct19 Oct24 Oct29 Oct

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

PLAN

Wipe schedule

too few wipes seen yet

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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 4 Oct, 17:06 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 schedule

What happens on Rozpierducha PL [Solo|2x] when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

When does Rozpierducha PL [Solo|2x] wipe?

The rhythm of Rozpierducha PL [Solo|2x]'s wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 24 days 21 hours ago the current world was made.

Lists and filters

Which tags does Rozpierducha PL [Solo|2x] carry, and what do they mean?

Tags published by Rozpierducha PL [Solo|2x], read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): 100 slots in total; ts1 (Group limit): You may team up with at most 1; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

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

On Rust Metrics, Rozpierducha PL [Solo|2x] sits in these lists: 2x Rust servers, checked live, EU Rust servers, checked, Modded Rust servers, checked live and Solo-only Rust servers. Check: filters. On the server list it appears under these: Region: Europe; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Solo; Gather rate: 2x.

Occupancy

What position does Rozpierducha PL [Solo|2x] hold among Rust servers?

Player hours over seven days put Rozpierducha PL [Solo|2x] at #12,352, in the top 55% of all ranked servers. Check: group rank. #189 among solo servers.

How full does Rozpierducha PL [Solo|2x] get?

Current headcount on Rozpierducha PL [Solo|2x]: 0 players, 100 slots available. Check: players over seven days. Average 0, peak 1. Check: 48-hour peak. 23:00 UTC, 1 players on average.

Server

Where does Rozpierducha PL [Solo|2x] sit?

The name of Rozpierducha PL [Solo|2x] points to Europe, though it publishes no region tag. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 157.157.78.137:28015.

What Rust version is Rozpierducha PL [Solo|2x] on?

Reading: Rozpierducha PL [Solo|2x], Rust network protocol 2635 and build 168909, Linux. Check: protocol. To join, your game must match; Steam handles the update.

What is the performance reading for Rozpierducha PL [Solo|2x]?

Check: fps. Average 117 server fps over the last 48 hours, low of 101. Within range. Check: entities. The peak was 66,267, counting buildings, deployables and the rest of the world. Reading: 3,044 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.

How reliable is Rozpierducha PL [Solo|2x], and is it online now?

Rozpierducha PL [Solo|2x] reports online. Status: normal. Check: restart. The uptime it reports puts the last restart about 3 days 22 hours ago. Uptime for the last 7 full days: 167 of 168 hours, or 99%. Check: first contact. Rust Metrics logged it on 3 October 2026.

Settings and map

What settings and rules apply on Rozpierducha PL [Solo|2x]?

The name carries the rate: 2x gather on Rozpierducha PL [Solo|2x]. Solo play only. Teams are not allowed. survival, the normal game: build, gather, raid — that is the game mode. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

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

Size 3,500 and seed 1337: the game generates the procedural map on Rozpierducha PL [Solo|2x] from them. The map repeats when size and seed match. Open it on RustMaps from this page.

Connection

How can you get onto Rozpierducha PL [Solo|2x]?

Press F1 in Rust and enter client.connect 157.157.78.137:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players 100 slots in total.
ts1
Group limit You may team up with at most 1.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is 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.