RUST METRICSFlight deck · live data
Data live Servers11,702 Players66,491 Populated3,572 Fresh wipes 3 h116 Scan5 min
‹ All servers103.91.208.231:20001
Offline Full Queue Fresh wipe Wipe due No query

咕嘎-test

Offline EA 103.91.208.231:20001 checked 15d ago

monthly wipes moddedoxidepve
COM 1 · connect

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 0 /100

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,509top 71% · #497 in EA
Last wipe24d agomonthly schedule
Next wipe8d 7hThu 5 Nov, 19:00 UTC FW
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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
15k10k15k20k20 Sep26 Sep2 Oct7 Oct13 Oct19 Oct

Top 71% of all ranked servers, top 92% in EA. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 8d 7h. The force wipe · high confidence

usual gap1 daysbetween real wipes
on rhythm38%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC8d 7hFW
  2. WPT 2Thu 3 Dec, 19:00 UTC36d 7hFW

The first 48 hours of its last wipes

Sun 4 OctThu 1 OctTue 29 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 2 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 4 Oct, 08:50 UTC24d ago 1 – running 1
Thu 1 Oct, 11:57 UTC26d ago 1 held half 2.9 days 1
Tue 29 Sep, 16:02 UTC28d ago 1 – 1.8 days 1
Mon 28 Sep, 19:36 UTC29d ago 1 – 0.9 days 1
Sun 27 Sep, 18:14 UTC30d ago 1 – 1.1 days 1
Sat 26 Sep, 16:37 UTC31d ago 1 – 1.1 days 1
Sat 26 Sep, 08:56 UTC32d ago 1 – 0.3 days 1
Fri 25 Sep, 21:58 UTC32d ago 1 – 0.5 days 1
Fri 25 Sep, 02:49 UTC33d ago 1 – 0.8 days 1
Thu 24 Sep, 20:18 UTC33d ago 1 – 0.3 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

Reset cycle

What should you expect from wipe day on 咕嘎-test?

An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 2 hours in. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

What wipe timing does 咕嘎-test follow?

Once a month 咕嘎-test wipes, with the force wipe. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. The world in play was created 24 days 3 hours ago. The tags state a wipe schedule of one wipe a month.

Tag meanings

How should you read the tags on 咕嘎-test?

Tags published by 咕嘎-test, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): Slots: 100; ts6 (Group limit): Teams are capped at 6; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167398 (Build): The server runs game build 167398; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^m (Monthly): Facepunch's force wipe sets the monthly cycle here; ^p (PvE): Check: mode. PvE, so the world supplies the danger, not other players; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Modded: plugins or settings depart from the stock game; EA (East Asia): The server browser files it under East Asia. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Who operates 咕嘎-test?

Most likely the same operator runs them: 咕嘎-test publishes a luxiaoxiong.top hostname, and so do 2 other servers we track.

Which lists and filters on Rust Metrics show 咕嘎-test?

Rust Metrics lists featuring 咕嘎-test: Modded Rust servers, checked live and Rust PvE servers. Check: filters. On the server list it appears under these: Region: Asia; Type: Modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.

Player count

Where does 咕嘎-test sit in the rankings?

Player hours over the last seven days put 咕嘎-test at #15,509, #497 in Asia, in the top 71% of all ranked servers.

What is the population on 咕嘎-test?

Status for 咕嘎-test: offline. Last seen 15 days 19 hours ago.

Operator and location

What location is 咕嘎-test hosted in?

Its EA tag places 咕嘎-test in Asia. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 103.91.208.231:20001.

What Rust version is 咕嘎-test on?

Reading: 咕嘎-test, Rust network protocol 2634 and build 167398, Windows. Matching protocol is required to join. Let Steam update your game.

What is the uptime on 咕嘎-test, and is it online?

Check: connection. 咕嘎-test is offline at this moment. Last contact was 15 days 19 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.

Rules and settings

How is 咕嘎-test configured, and what rules are in force?

Reading the name gives no gather rate for 咕嘎-test. Check: group limit. Up to 6 players. Mode check gives pve; no combat against other players. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on 咕嘎-test?

Size 4,300 and seed 1337: the game generates the procedural map on 咕嘎-test from them. View it on RustMaps from this page: matching size and seed give an identical map. Its map carries the name [无假人]特色玩家基地.

Join

How do you connect to 咕嘎-test?

Check: join. Open Rust, press F1, then enter client.connect 103.91.208.231:20001. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. You can find its website at https://qun.qq.com/universal-share/share?ac=1&authKey=hpBtsiFaMXzeA%2B5AiwcabBShzJgfEEkhOsTV1aFRDY1TqlIhnfCF1WzHkvpz3vPK&busi_data=eyJncm91cENvZGUiOiIxMDk0ODU1MTQwIiwidG9rZW4iOiJPc1NuY0s1alNtNU1XSkZHR0cvNHNQQllHK0ZKcEFvS2U5NlVuTFNzNGc4YkU0WjAzbkpKSEloUEU0MjIxK0hxIiwidWluIjoiMTgyNzY4ODU3OSJ9&data=ZBnHqnSF-0BlWzRzaJPL58nGsP6XATsrdsH3lPtkp8Ni-H1F3kc6v6t9X8s7gyLugU863f6h1FeEPl2lXd_o7pGJSNrNSiwQG7mU5gPQWPY&svctype=5&tempid=h5_group_info.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2634,^m,EA,^p,gmrust,cs167398,ts6,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp100
Max players Slots: 100.
ts6
Group limit Teams are capped at 6.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167398
Build The server runs game build 167398.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

Wipe schedule

^m
Monthly Facepunch's force wipe sets the monthly cycle here.

Gameplay

^p
PvE Check: mode. PvE, so the world supplies the danger, not other players.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Modded: plugins or settings depart from the stock game.

Region

EA
East Asia The server browser files it under East Asia.

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.