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

#2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥

123.192.255.191:28015 checked 10m ago

10x biweekly wipes moddedoxide
Deploy
Zerg meter7%light
4/60 troops
7-day average1
peak 7
Rank#3,251
top 15%
Last wipe12d ago
biweekly schedule
Next wipe · H-hour1d 17h
Fri 16 Oct, 06:52 UTC

Players

AveragePeak
0246814:0021:0005:0012:0005:0012:00

Hourly average and peak, UTC.

Server performance

010020030040014:0021:0005:0012:0005: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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep25 Sep30 Sep4 Oct9 Oct14 Oct

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

Wipe schedule

from its schedule tag

Next wipe Friday 16 October, 06:52 UTC, in 1d 17h. Its biweekly schedule tag · low confidence

usual gap7 days
between real wipes
on rhythm0%
of its recent wipes
wipe-day peak4
players, last three wipes
crowd held50%
else halves by day 7

Coming wipes

1d 17hFri 16 Oct, 06:52 UTC
15d 17hFri 30 Oct, 06:52 UTC
22d 5hThu 5 Nov, 19:00 UTCFW
29d 17hFri 13 Nov, 06:52 UTC
43d 17hFri 27 Nov, 06:52 UTC

The first 48 hours of its last wipes

Fri 2 OctSun 27 SepFri 18 Sep
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 5, 31 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 06:52 UTC12d ago 5 – running 0
Sun 27 Sep, 08:17 UTC17d ago 3 held half 4.9 days 0
Fri 18 Sep, 05:51 UTC26d ago 4 halved by day 7 9.1 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 32
JumpRust.com - 戦え! 5x|JP/SEA|PVP+PVE|Events|Shop|Kits|TP EA · groups of 32+ · 5x · biweekly · 16 on average
22/120
Zergmax 12
[TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/02 EA · groups of 12+ · 5x · biweekly · 4 on average
0/200
No limit8 · game default
[SEA] AseanPanda.net | 2x Vanilla | MAP WIPE 3 | 13/10 EA · groups of 8+ · 2x · biweekly · 73 on average
127/165
Zergmax 10
[JP]初心者PVPサーバー|RaidTime・ Events EA · groups of 10+ · biweekly · 6 on average
10/100
No limit8 · game default
[SEA] Rust Manila 2x | Biweekly EA · groups of 8+ · 2x · biweekly · 4 on average
5/150
Teams offteams disabled
[JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/2~10/15 EA · no group limit · biweekly · 3 on average
4/20

Quick answers

from the figures on this page

Server rules

Which settings and rules apply on #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥?

#2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥 goes by 10x gather, as its name says. The group cap is 8 players, the default for the game. survival is its mode, gather, build, raid: the regular game. Other players can be fought and raided. The server browser lists it under Modded: the game is changed by plugins or settings. The plugins it runs number Oxide. VAC is on, Valve's anti-cheat.

Which map is active on #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥?

Size 4,500, seed 1683482379, generated by the game: the procedural map on #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥. Same size and seed, same map: RustMaps shows it from this page.

Player count

How full is #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥?

#2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥 has 4 of its 60 slots filled right now. Its weekly average is 1 players and its highest point was 7. The busiest time in the last 48 hours was 14:00 UTC, when it averaged 7 players.

What is #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥's ranking?

In the top 15% of ranked servers, #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥 holds #3,251 for player hours over the last seven days.

Lists and tags

What do #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥's tags indicate?

For the game's server browser, #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥 publishes these tags: gmrust (Game mode): Standard survival gameplay; mp60 (Max players): Capacity: 60; ts8 (Group limit): This uses the standard team limit of 8; v2634 (Protocol): Protocol 2634—only players on that version can get in; cs166494 (Build): The game build is 166494; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): No region code is set; ^b (Biweekly): Every two weeks the server wipes; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): Modded category: the game is altered by plugins or settings. At the top of this page you see its players now, its queue and the time its world was made, which are in the tags too.

Which Rust Zerg Life filters and lists cover #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥?

The Rust Zerg Life lists that include #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥 are 10x Rust servers for clans and zergs and Modded Rust servers for clans and zergs. These filters bring it up on the server list: Region: Asia; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks; Gather rate: 10x.

Server info

What is the uptime and reliability of #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥?

#2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥 is up and running as you read this. Based on the uptime it reports, the last restart was about 3 hours ago. It was up 98% of the time across the last 7 full days: 164 of 168 hours. Rust Zerg Life has been tracking it since 13 September 2026.

What is the performance like on #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥?

Server fps held an average of 148 for the last 48 hours, with a minimum of 53. The world held as many as 158,861 entities, including buildings, deployables and everything else. The maximum memory it used was 4,433 MB. What players experience as lag comes from low fps and a rising entity count.

What version is #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥 using?

Rust network protocol 2634 and build 166494 is what #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥 runs, on Windows. Joining requires your game to be on the same protocol, which Steam updates automatically.

What is the location of #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥?

Without a region tag from #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥, its name still points to Asia. Rust Zerg Life displays the location a server claims, not where the machine actually stands. You can reach it at 123.192.255.191:28015.

Wipe schedule

What can you expect on wipe day on #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥?

Across its recent wipes, the busiest times averaged 4 players. 31 hours after the latest wipe, the crowd peaked. Until the next wipe, the crowd stayed above half that peak in 50% of its recent wipes. If not, the crowd fell below half by day 7.

When does #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥 wipe?

With too few wipes recorded to confirm #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥's schedule, the prediction comes from its tag. It is due to wipe next on Friday 16 October at 06:52 UTC. 12 days 6 hours ago is when its present world was created. A wipe every two weeks is published in its tags.

Connect

What steps do I take to join #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥?

You can join by opening the console with F1 and typing client.connect 123.192.255.191:28015. Or hit Launch Rust on this page to open Rust through Steam and connect.

Server tags

what each one means

Published as mp60,ptrak,$r?,v2634,^b,gmrust,cs166494,ts8,^o^z

Game

gmrust
Game mode Standard survival gameplay.
mp60
Max players Capacity: 60.
ts8
Group limit This uses the standard team limit of 8.
v2634
Protocol Protocol 2634—only players on that version can get in.
cs166494
Build The game build is 166494.
ptrak
Networking It uses RakNet, the standard network layer for the game.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly Every two weeks the server wipes.

Mods and access

^o
Oxide This server uses Oxide (uMod) for plugins.
^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.