#2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO
Key statistics
the figures behind the quote- Players now
- 0/ 100 0% full
- Change · 24h
- ▪+0 no reading a day ago
- 7-day average
- 0 peak 2
- Rank
- #7,413 top 33%
- Rank · 7d ago
- #8,208 ▲795 places up
- Last wipe
- 3d ago no schedule published
- Next wipe
- – no rhythm it keeps
- Group limit
- 8 8, the default
- Gather rate
- 2x read from the name
- Score
- 15 player hours, last seven days
- Map
- 4000 Procedural Map · seed 421948
- First seen
- 13 Sep 2026 no hostname published
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC. Busiest hour of the two days: 2 players.
Daily average and peak, UTC.
Server performance
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 bestTop 33% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keeps- usual gap
- 9.6 days between real wipes
- on rhythm
- 100% of its recent wipes
- wipe-day peak
- 2 players, last three wipes
- crowd held
- 0% else halves by day 6.5
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players 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| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | Atlas - EU 2X Monthly | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · monthly · 621 on average | 578/650 | ▼−153−20.9% | |
| 2 | Vital Rust - EU Monthly | 2x | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · monthly · 401 on average | 368/375 | ▼−98−21.1% | |
| 3 | MIRAGE RUST | MONTHLY 2x | VANILLA+ | Wipe 01.10EU · groups of 300+ · 2x · monthly · 296 on average | 518/600 | ▼−17−3.2% | |
| 4 | MIRAGE RUST | MAIN 2x | VANILLA+ | Wipe 09.10EU · groups of 300+ · 2x · weekly · 294 on average | 46/1000 | ▼−25−34.9% | |
| 5 | Magic Rust #18 — Vanilla 2x | Baйп 14.10EU · groups of 150+ · 2x · weekly · 248 on average | 1285/1500 | ▲+1244+3034.1% | |
| 6 | Magic Rust #27 — Vanilla 2x (Monthly) | PyccкийEU · groups of 150+ · 2x · monthly · 245 on average | 284/320 | ▼−47−14.1% |
Quick answers
from the figures on this pageMap and Rules
How is #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO configured in terms of rules and settings?
#2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO carries its gather rate in its name: 2x. Up to 8 players per group, which is the game's default. It runs survival, gather, build and raid in the standard game. Combat and raiding between players are allowed. The server browser lists it as Modded: plugins or settings change the game. Oxide plugins are running. VAC is active.
Which map is played on #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO?
#2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO uses a procedural map of size 4,000 with seed 421948, generated by the game. You can see the map on RustMaps from this page, as the same size and seed give the same map.
Population
Where does #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO sit in the rankings?
For the last seven days, #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO holds rank #7,413 on player hours, in the top 33% of all ranked servers.
What is the population on #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO?
0 of 100 slots on #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO are filled right now. The mean over the last seven days is 0 players, reaching 2 at its highest. Over the last 48 hours, the peak hour was 13:00 UTC, averaging 2 players.
Wipe Schedule
How does #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO handle wipe day?
The average peak across its recent wipes is 2 players. On the latest wipe, 0 hours after the wipe, the crowd peaked. Half the peak was held until the next wipe in 0% of its recent wipes. The crowd fell below half by day 6.5 when it did not hold.
When does #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO schedule its wipes?
No next wipe can be predicted for #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO: it wipes at irregular times. The monthly force wipe applies to every Rust server. The next one falls on Thursday 5 November at 19:00 UTC. Its world now is 3 days 18 hours old.
Server Details
What is the location of #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO?
No region is published by #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO. Rust Analytics reports the location a server claims, not the machine's actual location. You can reach it at 188.243.102.226:28035.
Is #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO performing well?
Server fps over the last 48 hours: 103 on average, 36 at the lowest. 94,610 entities is the maximum carried: buildings, deployables and everything else. The memory ceiling reached 3,770 MB. Low fps and growing entities are the source of felt lag.
What Rust version is #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO running?
Rust network protocol 2634 and build 167781 on Windows is what #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO runs. Your game needs the same protocol to get in; Steam takes care of the update.
Is #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO up, and how consistent is its uptime?
The server is live: #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO is online. 6 hours ago is when it last restarted, judging by the uptime it reports. 67% is its uptime for the last 7 full days, 112 of 168 hours. The earliest Rust Analytics saw it was 13 September 2026.
Tags and Rankings
What is the meaning of the tags on #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO?
Published by #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO for the game's server browser to read: gmrust (Game mode): Rust's standard survival mode; mp100 (Max players): Capacity: 100 slots; ts8 (Group limit): 8 per team: the default setting, unchanged; v2634 (Protocol): Your game must run protocol 2634 to connect; cs167781 (Build): Build 167781; ptrak (Networking): The standard network layer, RakNet; $r? (Region code): The region code is absent; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The Modded listing applies: plugins or settings change play. The top of this page and the tags both show its players now, its queue and when its world was made.
#2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO appears in which of the lists and filters on Rust Analytics?
The following Rust Analytics lists feature #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO: 2x Rust servers and Modded Rust servers. These filters bring it up 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.
Joining the Server
What steps do I take to join #2 PANDORUM MAX3 | X2 | SOLO/DUO/TRIO?
Type client.connect 188.243.102.226:28035 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you.
Server tags
what each one meansPublished as mp100,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z
Game
gmrust
mp100
ts8
v2634
cs167781
ptrak
$r?
Mods and access
^o
^z
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.