RUST ZERG LIFEClan war room · live
No limit8 · game default
Deployment dossierOnline

#2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO

188.243.102.226:28035 checked 10m ago

2x moddedoxide
Deploy
Zerg meter1%light
1/100 troops
7-day average0
peak 1
Rank#9,048
top 41%
Last wipe3d ago
no schedule published
Next wipe · H-hour–
no rhythm it keeps

Players

AveragePeak
00.250.50.75110:0017:0001:0008:0016:0008:00

Hourly average and peak, UTC.

Server performance

05010015020010:0017:0001:0008:0016:0008: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 21 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep25 Sep30 Sep4 Oct9 Oct14 Oct

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

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap9.6 days
between real wipes
on rhythm100%
of its recent wipes
wipe-day peak2
players, last three wipes
crowd held0%
else halves by day 6.5

The first 48 hours of its last wipes

Sat 10 OctThu 1 OctMon 21 Sep
00.511.52+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
WipedPeakCrowdLastedPlayers before
Sat 10 Oct, 21:41 UTC3d ago 1 – running 0
Thu 1 Oct, 18:26 UTC FW12d ago 2 halved by day 6 9.1 days 0
Mon 21 Sep, 18:12 UTC22d ago 2 halved by day 7 10 days 1

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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
Zergmax 16
Atlas - EU 2X Monthly | Vanilla+ | No BP Wipes EU · groups of 16+ · 2x · monthly · 640 on average
319/350
Zergmax 16
Vital Rust - EU Monthly | 2x | Vanilla+ | No BP Wipes EU · groups of 16+ · 2x · monthly · 417 on average
174/175
Zergmax 300
MIRAGE RUST | MONTHLY 2x | VANILLA+ | Wipe 01.10 EU · groups of 300+ · 2x · monthly · 300 on average
193/500
Zergmax 300
MIRAGE RUST | MAIN 2x | VANILLA+ | Wipe 09.10 EU · groups of 300+ · 2x · weekly · 293 on average
21/1000
Zergmax 150
Magic Rust #18 — Vanilla 2x | Pyccкий EU · groups of 150+ · 2x · weekly · 260 on average
16/100
Zergmax 150
Magic Rust #27 — Vanilla 2x (Monthly) | Pyccкий EU · groups of 150+ · 2x · monthly · 253 on average
153/300

Quick answers

from the figures on this page

Map and rules

Which settings and rules apply on #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO?

Its name says 2x gather, and that is what #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO runs. That is the game's default: groups of up to 8 players. It runs survival, the usual game of gathering, building and raiding. You can fight and raid other players here. Plugins or settings change the game, and it is listed under Modded in the server browser. It runs plugins: Oxide. Anti-cheat is on: VAC, from Valve.

Which map is active on #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO?

The game generates the procedural map of size 4,000 on #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO with seed 421948. From this page, RustMaps can show it: size and seed produce the same map each time.

Population

How many players are on #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO?

The server #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO is currently at 1 players out of 100 slots. Its weekly average is 0 players and its highest point was 1. The busiest time in the last 48 hours was 22:00 UTC, when it averaged 1 players.

Where does #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO sit in the rankings?

In the top 41% of ranked servers, #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO holds #9,048 for player hours over the last seven days.

Tags and filters

What do #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO's tags indicate?

For the game's server browser, #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO publishes these tags: gmrust (Game mode): Survival in the standard Rust mode; mp100 (Max players): It holds 100 players; ts8 (Group limit): This uses the standard team limit of 8; v2634 (Protocol): You'll need protocol 2634 on your game to join; cs167781 (Build): Build number: 167781; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): There's no region code here; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Modded category: the game is altered by plugins or settings. Also in the tags: its players now, its queue and the time its world was made, and the top of this page shows them.

Where does #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO appear in Rust Zerg Life lists?

These Rust Zerg Life lists include #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO: 2x Rust servers for clans and zergs and Modded Rust servers for clans and zergs. Under these filters it shows on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week; Gather rate: 2x.

Server info

How reliable is #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO, and is it up?

You can join #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO now: it is online. Based on the uptime it reports, the last restart was about 15 hours ago. Over the last 7 full days, uptime was 67%: 112 hours up out of 168. Rust Zerg Life has been tracking it since 13 September 2026.

What is the performance like on #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO?

It averaged 97 server fps over the last 48 hours, and the lowest it got was 36. The world held as many as 92,370 entities, including buildings, deployables and everything else. At its highest, memory usage hit 3,770 MB. A climbing entity count and low fps are the source of the lag players feel.

What version is #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO using?

Rust network protocol 2634 and build 167781 is what #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO runs, on Windows. Joining requires your game to be on the same protocol, which Steam updates automatically.

What is the location of #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO?

There is no region published by #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO. Rust Zerg Life displays the location a server claims, not where the machine actually stands. You can reach it at 188.243.102.226:28035.

Wipe days

What happens on wipe day on #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO?

At their busiest, its recent wipes drew an average of 2 players. On the latest wipe, 0 hours after the wipe, the crowd hit its peak. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. If not, the crowd fell below half by day 6.5.

When does #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO wipe?

#2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO wipes without a set pattern, so there is no upcoming wipe to forecast. The monthly force wipe hits every Rust server, and on Thursday 5 November at 19:00 UTC it is due next. The world it is running now dates from 3 days 11 hours ago.

How to join

What steps do I take to join #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO?

Enter client.connect 188.243.102.226:28035 in the F1 console. Another way: use Launch Rust on this page, which opens Rust through Steam and connects you.

Server tags

what each one means

Published as mp100,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Survival in the standard Rust mode.
mp100
Max players It holds 100 players.
ts8
Group limit This uses the standard team limit of 8.
v2634
Protocol You'll need protocol 2634 on your game to join.
cs167781
Build Build number: 167781.
ptrak
Networking It uses RakNet, the standard network layer for the game.
$r?
Region code There's no region code here.

Mods and access

^o
Oxide Plugins run through Oxide (uMod).
^z
Modded Modded category: the game is altered 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.