Offline EA 1.81.212.187:28015 checked 41d ago
LU测试服
Connect
srv = rust.server("1.81.212.187: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 best
Wipe schedule
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 7d 0h. # The force 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.187:28015
- region
- EA
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- biweekly
- last wipe
- 17 Sep 2026, 00:58 UTC
- hostname
- –
- first seen
- 18 Sep 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 · 15 on average | 2/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 | 2/100 |
| 3 | [JP/PvE][BPリサーチ]MatoyServer初しん者〇 | EA · groups of 8+ · biweekly · 2 on average | 0/50 |
| 4 | [JPN] Apple Server | PvP | Vanilla | 2Weekly | EA · groups of 8+ · biweekly · 2 on average | 1/50 |
| 5 | cczsbwd/solo/独狼/原倍半月清/月图/公益服 | EA · no group limit · biweekly · 2 on average | 1/50 |
Quick answers
From the figures on this page.
Player counts
How does LU测试服 compare in the rankings?
Ranked #13,268 on seven-day player hours, LU测试服 is #461 in Asia and in the top – of all ranked servers.
How full does LU测试服 run?
LU测试服 returns no live count at this refresh, having last been seen 41 days 16 hours ago.
About the server
What Rust version does LU测试服 run?
The build is Rust network protocol 2633 and build 163794 on Windows, run by LU测试服. Joining needs the same protocol on your game; Steam handles the update.
How reliable is LU测试服, and is it online now?
Offline now for LU测试服, last seen 41 days 16 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 18 September 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.187:28015 is its address.
Settings and map
Which settings and rules does LU测试服 run?
You will not find a gather rate in the string LU测试服. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC is not running; Valve's anti-cheat is off.
Which map has LU测试服 selected?
The game generates its map: procedural, on LU测试服.
Wipe schedule
When does LU测试服 wipe, and on what schedule?
The next wipe for LU测试服 is an estimate, drawn from the force wipe. 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 generated 42 days 17 hours ago. The tags list a two-weekly wipe cycle.
Tags, lists
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.
How should you read the server tags on LU测试服?
Read by the game's server browser, the tags LU测试服 publishes are: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): Slot count: 100; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs163794 (Build): The server runs build 163794; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^b (Biweekly): Two weeks between wipes; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings; EA (East Asia): The server browser files it under East Asia. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
How can I connect to LU测试服?
The manual route: launch Rust, F1, then client.connect 1.81.212.187:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.