Offline EA 103.91.208.231:20001 checked 15d ago
咕嘎-test
Connect
srv = rust.server("103.91.208.231:20004")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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
srv.rank.plot(invert=True) # 1 is best
Top 71% of all ranked servers, top 92% in EA. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 8d 22h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 8d 22h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 36d 22h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 2 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 4 Oct, 08:50 UTC23d ago | 1 | NaN | running | 1 |
| 1 | Thu 1 Oct, 11:57 UTC26d ago | 1 | held half | 2.9 days | 1 |
| 2 | Tue 29 Sep, 16:02 UTC28d ago | 1 | NaN | 1.8 days | 1 |
| 3 | Mon 28 Sep, 19:36 UTC29d ago | 1 | NaN | 0.9 days | 1 |
| 4 | Sun 27 Sep, 18:14 UTC30d ago | 1 | NaN | 1.1 days | 1 |
| 5 | Sat 26 Sep, 16:37 UTC31d ago | 1 | NaN | 1.1 days | 1 |
| 6 | Sat 26 Sep, 08:56 UTC31d ago | 1 | NaN | 0.3 days | 1 |
| 7 | Fri 25 Sep, 21:58 UTC31d ago | 1 | NaN | 0.5 days | 1 |
| 8 | Fri 25 Sep, 02:49 UTC32d ago | 1 | NaN | 0.8 days | 1 |
| 9 | Thu 24 Sep, 20:18 UTC32d ago | 1 | NaN | 0.3 days | 1 |
| 10 | Wed 23 Sep, 14:24 UTC34d ago | 1 | NaN | 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.
display(srv.map, srv.info())
Operator · luxiaoxiong.top
rust.servers(operator="luxiaoxiong.top").sort_values("players")
| server | players | |
|---|---|---|
| 0 | [大熊PVE]-2倍/自动养殖/建造/突袭副本/死亡不掉 | 4/100 |
| 1 | [大熊PVE]二服/2倍/新养殖自动化/突袭/死亡不掉 | 0/100 |
3 servers publish a luxiaoxiong.top hostname.
About this server · in its own words
print(srv.description)
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | [凡人修仙传]PVE/修为/宗门/炼丹/硬核/装备成长 | EA · groups of 5 · monthly · 17 on average | 10/456 |
| 1 | 614《断剑》PVE 迷失暗黑|仙途重聚|直连进入 | EA · groups of 6 · 45 on average | 40/150 |
| 2 | Eri's Server JP-Only Season10.5 | EA · groups of 6 · 2 on average | 0/60 |
| 3 | [坚果PVE]宗门/合成/挂机/升级/召唤/副本/拍卖 | EA · groups of 8+ · monthly · 36 on average | 28/100 |
| 4 | 爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地 | EA · groups of 8+ · monthly · 21 on average | 19/88 |
| 5 | [熊猫PVE]修仙升级/召唤/据点/10月新档正式服 | EA · groups of 8+ · monthly · 12 on average | 12/100 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does 咕嘎-test rank?
On seven-day player hours 咕嘎-test is #15,509 overall and #497 in Asia, inside the top 71% of all ranked servers.
What population does 咕嘎-test carry?
The current row shows 咕嘎-test offline; the last response was 15 days 4 hours ago.
About the server
What is the Rust version on 咕嘎-test?
The build is Rust network protocol 2634 and build 167398 on Windows, run by 咕嘎-test. The protocol has to match before you can join, and Steam does the updating.
How reliable is 咕嘎-test, and is it online now?
The latest sample has 咕嘎-test offline, with a last sighting 15 days 4 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 13 September 2026.
In which location is 咕嘎-test hosted?
In Asia, 咕嘎-test lists itself, using the EA tag. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 103.91.208.231:20001.
Settings and map
Which settings and rules does 咕嘎-test run?
The name 咕嘎-test carries no gather rate. Group size tops out at 6 players. pve is the game mode here, and player combat is not allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has 咕嘎-test loaded?
咕嘎-test runs a procedural map of size 4,300 with seed 1337, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed. [无假人]特色玩家基地 is what the map name field says.
Wipe schedule
When does 咕嘎-test wipe, and on what schedule?
A single wipe each month, the force wipe, is all 咕嘎-test does. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. This world was created 23 days 11 hours ago. Its tags carry a monthly wipe schedule.
On 咕嘎-test, what happens on wipe day?
The average peak over recent wipes is 1 players. 2 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 100% of the time.
Lists and tags
Which Rust Data filters and lists contain 咕嘎-test?
On Rust Data, 咕嘎-test appears in these lists: Modded Rust servers and Rust PvE servers. Under these filters on the server list, it is listed: 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.
Which operator runs 咕嘎-test?
咕嘎-test and 2 other servers we track both publish a luxiaoxiong.top hostname, so the same operator most likely runs them.
How should you read the server tags on 咕嘎-test?
These tags are published by 咕嘎-test and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): The server lists 100 slots; ts6 (Group limit): The team cap is 6; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167398 (Build): The server runs build 167398; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^p (PvE): No player-versus-player combat; the danger comes from the world; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; EA (East Asia): In the server browser it sits under East Asia. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
What is the way to join 咕嘎-test?
Enter client.connect 103.91.208.231:20001 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. 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.
