RUST METRICSFlight deck · live data
Data live Servers11,849 Players73,470 Populated3,705 Fresh wipes 3 h219 Scan5 min
‹ All servers123.192.255.191:28015
Online Full Queue Fresh wipe Wipe due No query

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

Online 123.192.255.191:28015 checked 8m ago

10x biweekly wipes moddedoxide
COM 1 · connect

Server instruments

last reading Thu 12:00 UTC
0 15 30 45 60 PAX 0 /60

Players now

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

Server fps

48 h low 38 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 151,391 ×1000

Entities

48 h range 122,453–164,141 · memory 3,838 MB
1239 ET SINCE RESTART 05:56

Uptime

5 h 56 min since its last restart, at the last reading
7-day average1peak 9
Rank#3,153top 14%
Last wipe13d agobiweekly schedule
Next wipe19hFri 30 Oct, 09:05 UTC
Memory3,838MB48 h peak 3 players
REC 1

Players

AveragePeak
0123414:0021:0005:0012:0021:0012:00

Hourly average and peak, UTC.

REC 2

Server performance

010020030040014:0021:0005:0012:0021: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.

REC 3

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

PLAN

Wipe schedule

from its schedule tag

Next wipe Friday 30 October, 09:05 UTC, in 19h. Its biweekly schedule tag · low confidence

usual gap9.1 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak4players, last three wipes
crowd held33%else halves by day 6.5

Coming wipes

  1. WPT 1Fri 30 Oct, 09:05 UTC19h
  2. WPT 2Thu 5 Nov, 19:00 UTC7d 5hFW
  3. WPT 3Fri 13 Nov, 09:05 UTC14d 19h
  4. WPT 4Fri 27 Nov, 09:05 UTC28d 19h
  5. WPT 5Thu 3 Dec, 19:00 UTC35d 5hFW
  6. WPT 6Fri 11 Dec, 09:05 UTC42d 19h

The first 48 hours of its last wipes

Fri 16 OctFri 2 OctSun 27 Sep
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 4, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 09:05 UTC13d ago 4 – running 0
Fri 2 Oct, 06:52 UTC27d ago 5 halved by day 6 14.1 days 0
Sun 27 Sep, 08:17 UTC32d ago 3 held half 4.9 days 0
Fri 18 Sep, 05:51 UTC41d 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.

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 should you expect from wipe day on #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥?

The busiest point of its recent wipes drew 4 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe. The crowd stayed above half that peak until the next wipe in 33% of its recent wipes. When it didn't hold, by day 6.5 it fell below half.

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

Its tag guides the prediction: too few of #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥's wipes are on record to confirm its schedule. On Friday 30 October at 09:05 UTC its next wipe is due. The world in play was created 13 days 4 hours ago. Its tags publish a wipe schedule of one wipe every two weeks.

Tag meanings

How should you read the tags on #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp60 (Max players): 60 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^b (Biweekly): Two-week wipe schedule; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game from #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥 appear in Rust Metrics lists and filters?

On Rust Metrics, #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥 sits in these lists: 10x Rust servers and Modded Rust servers, checked live. Reading: server list filters. It comes up under 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.

Population

What position does #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥 hold among Rust servers?

Ranking for #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥: #3,153 on seven-day player hours, top 14% of all ranked servers.

What player count does #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥 carry?

Current headcount on #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥: 0 players, 60 slots available. Seven-day check: 1 players on average. Peak reading: 9. Average at the busiest hour was 2 players, at 08:00 UTC over the last 48 hours.

Operator and location

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

The name of #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥 points to Asia, though it publishes no region tag. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 123.192.255.191:28015.

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

Reading: #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥, Rust network protocol 2635 and build 168909, Windows. Check: protocol. To join, your game must match; Steam handles the update.

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

Reading: 191 server fps on average across the last 48 hours. It never dropped below 38. Reading: 164,141 entities at the highest. That covers buildings, deployables and everything else. Reading: 4,588 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.

Is #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥 up, and how often does it stay up?

Reading: online. #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥 answers right now. By its reported uptime, the last restart was roughly 5 hours ago. Uptime for the last 7 full days: 159 of 168 hours, or 95%. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Map and rules

How is #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥 configured, and what rules are in force?

Gather rate check: 10x. That comes from the name #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Oxide of them. VAC is on. That is Valve's anti-cheat.

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

Check: map. Procedural, size 4,500, seed 1673229444, generated by the game on #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥. View it on RustMaps from this page: matching size and seed give an identical map.

How to join

How can you get onto #2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥?

To join: start Rust, press F1 and type client.connect 123.192.255.191:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp60,ptrak,$r?,v2635,^b,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp60
Max players 60 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build The server runs game build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly Two-week wipe schedule.

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.