Fig. 1Players on 咕嘎-testRG-S15509-01 · Sheet 1 of 12
Fig. 2
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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.
Fig. 2FPS, entities and memoryRG-S15509-02 · Sheet 2 of 12
Fig. 3
Rank
daily · 1 is best
RankRank in region
Top 71% of all ranked servers, top 92% in EA. Ranked on player hours over the last seven days.
Fig. 3Rank on player hours, dailyRG-S15509-03 · Sheet 3 of 12
Schedule
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 22h.
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
7d 22hThu 5 Nov, 19:00 UTCFW
35d 22hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Sun 4 OctThu 1 OctTue 29 Sep
Fig. 4Players each hour from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 1, 2 hours in.
ScheduleExpected wipesRG-S15509-04 · Sheet 4 of 12
Log
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 4 Oct, 08:50 UTC24d ago
1
–
running
1
Thu 1 Oct, 11:57 UTC27d ago
1
held half
2.9 days
1
Tue 29 Sep, 16:02 UTC29d ago
1
–
1.8 days
1
Mon 28 Sep, 19:36 UTC30d ago
1
–
0.9 days
1
Sun 27 Sep, 18:14 UTC31d ago
1
–
1.1 days
1
Sat 26 Sep, 16:37 UTC32d 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 UTC34d ago
1
–
0.3 days
1
Wed 23 Sep, 14:24 UTC35d ago
1
–
1.2 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.
Table 1Wipe logRG-S15509-05 · Sheet 5 of 12
Similar assemblies
Similar servers
the same kind of game, then region, group limit, rate and wipes
Is 咕嘎-test online, and what uptime has been recorded?
Last seen 16 days 4 hours ago; right now 咕嘎-test is offline. 0 of 168 hours up over the last 7 full days, which is 0% of the time. The first sighting of it by Rust Graphs was on 13 September 2026.
2.
What location is recorded for 咕嘎-test?
With its EA tag, 咕嘎-test lists itself in Asia. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. 103.91.208.231:20001 is its address.
3.
What Rust version is recorded for 咕嘎-test?
On Windows, 咕嘎-test runs Rust network protocol 2634 and build 167398. To join, your game must be on the same protocol; Steam handles the update.
Population
4.
What player count is recorded on 咕嘎-test?
咕嘎-test is not responding at the latest refresh; the last record of it online is 16 days 4 hours ago.
5.
Against other Rust servers, where is 咕嘎-test placed?
Across seven days, player hours give 咕嘎-test #15,509 globally and #497 in Asia, a top 71% position among ranked servers.
Wipe times
6.
What is recorded on 咕嘎-test on wipe day?
The recent wipes averaged a busiest count of 1 players. 2 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 100% of its recent wipes.
7.
On 咕嘎-test, when do wipes occur?
Once a month, with the force wipe, is when 咕嘎-test wipes. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world it runs now was made 24 days 12 hours ago. The tags state a wipe schedule of one wipe a month.
Map and rules
8.
What settings and rules apply on 咕嘎-test?
The name of 咕嘎-test records no gather rate. The group limit is 6 players. It runs the pve game mode, no fighting other players. Listed as Modded in the server browser: the game is changed by plugins or settings. The plugin count is Oxide. VAC is on: that is Valve's anti-cheat.
9.
On which map is 咕嘎-test played?
Size 4,300 with seed 1337: that is the procedural map 咕嘎-test runs, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing. The name of the map reads: [无假人]特色玩家基地.
Filters
10.
Where does 咕嘎-test appear among the Rust Graphs lists and filters?
The Rust Graphs lists that carry 咕嘎-test are: Modded Rust servers and PvE Rust servers, plotted. These filters on the server list return it: 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.
11.
Which meaning is attached to each tag on 咕嘎-test?
Tags published by 咕嘎-test, and read by the game's server browser: gmrust (Game mode): Standard survival, as Rust plays; mp100 (Max players): 100 player slots; ts6 (Group limit): The team limit is 6; v2634 (Protocol): To join, your game must be on protocol 2634; cs167398 (Build): The game build is 167398; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is recorded; ^m (Monthly): Monthly wipes, on Facepunch's force wipe; ^p (PvE): Player fights are off; the world supplies the danger; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it is listed under Modded; EA (East Asia): The browser's listing places it under East Asia. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
12.
Who is the operator of 咕嘎-test?
The same operator most likely runs 咕嘎-test and 2 other servers we track, since all publish a luxiaoxiong.top hostname.
Connect
13.
What is the way to connect to 咕嘎-test?
Enter client.connect 103.91.208.231:20001 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you. You will 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.
NotesAnswered from the figuresRG-S15509-11 · Sheet 11 of 12
Key
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,^m,EA,^p,gmrust,cs167398,ts6,^o^z
Game
gmrust
Game modeStandard survival, as Rust plays.
mp100
Max players100 player slots.
ts6
Group limitThe team limit is 6.
v2634
ProtocolTo join, your game must be on protocol 2634.
cs167398
BuildThe game build is 167398.
ptrak
NetworkingThe network layer is RakNet, the game's standard.
$r?
Region codeNo region code is recorded.
Wipe schedule
^m
MonthlyMonthly wipes, on Facepunch's force wipe.
Gameplay
^p
PvEPlayer fights are off; the world supplies the danger.
Mods and access
^o
OxideThe plugin framework is Oxide (uMod).
^z
ModdedPlugins or settings change the game, so it is listed under Modded.
Region
EA
East AsiaThe browser's listing places 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.
KeyTag string decodedRG-S15509-12 · Sheet 12 of 12
