Offline EA 1.81.212.200:28015 checked 6d ago
LU测试服
Connect
srv = rust.server("1.81.212.200:28017")
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. 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 bestTop 69% of all ranked servers, top 90% in EA. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Next wipe Friday 30 October, 09:40 UTC, in 23h. # Biweekly: 14 days after its last wipe
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 1.81.212.200:28015
- region
- EA
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- biweekly
- last wipe
- 16 Oct 2026, 09:40 UTC
- hostname
- –
- first seen
- 22 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ［JP］初心者PVPサーバー｜RaidTime・ Events | EA · groups of 10+ · biweekly · 16 on average | 3/100 |
| 1 | [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29 | EA · no group limit · biweekly · 4 on average | 1/20 |
| 2 | 瞌睡熊『5倍10废|10.29|萌新首选|无权限』 | EA · groups of 8+ · biweekly · 4 on average | 3/100 |
| 3 | [JPN] Apple Server | PvP | Vanilla | 2Weekly | EA · groups of 8+ · biweekly · 2 on average | 1/50 |
| 4 | [JP/PvE][BPリサーチ]MatoyServer初しん者〇 | EA · groups of 8+ · biweekly · 2 on average | 5/50 |
| 5 | Rustoria.co - SEA Medium | EA · groups of 16+ · biweekly · 64 on average | 287/275 |
Quick answers
From the figures on this page.
Player counts
What position does LU测试服 take in the server rankings?
Player hours over the last seven days: #15,335 for LU测试服, #501 in Asia, within the top 69% of the ranked set.
How full does LU测试服 run?
The current row shows LU测试服 offline; the last response was 6 days 19 hours ago. Over the last seven days it averaged 0 players.
Server facts
Which Rust version is LU测试服 on?
Rust network protocol 2634 and build 167781 on Windows is what LU测试服 runs. Steam updates your game for you, but the protocol must match to join.
How reliable is LU测试服, and is it up?
LU测试服 is offline at this refresh; the last response came 6 days 19 hours ago. 0 of 144 hours up over the last 6 full days, or 0%. Rust Data logged it first on 22 October 2026.
Which location does LU测试服 run from?
The EA tag is what LU测试服 uses to list itself in Asia. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 1.81.212.200:28015 is its address.
Settings and map
Which settings and rules does LU测试服 run?
No gather rate appears in the name: LU测试服. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the base game, where you gather, build and raid. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. The VAC field reads off.
Which map has LU测试服 loaded?
A procedural map runs on LU测试服, generated by the game.
Wipe data
When does LU测试服 wipe, and on what schedule?
An estimate from biweekly: 14 days after its last wipe gives LU测试服's next wipe. The schedule puts the next wipe on Friday 30 October at 09:40 UTC. A new world was started 13 days ago, and that is the one in play. A fortnightly wipe schedule is published in its tags.
Tags and filters
Where does LU测试服 appear among Rust Data lists and filters?
On Rust Data, LU测试服 appears in these lists: Modded Rust servers. It appears under these filters 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.
Which meanings do the tags on LU测试服 hold?
The game's server browser reads these tags from LU测试服: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): Slot count: 100; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^b (Biweekly): Two weeks between wipes; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; EA (East Asia): East Asia is its listing in the server browser. 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.
How to join
How can I connect to LU测试服?
In Rust, F1 opens the console: type client.connect 1.81.212.200:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.