Offline EA 1.81.213.251:28015 checked 13d ago
LU测试服
Connect
srv = rust.server("1.81.213.251: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 60% of all ranked servers, top 88% 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 11h. # 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.213.251: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
- 16 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 · 14 on average | 0/100 |
| 1 | 瞌睡熊『5倍10废|10.30|萌新首选|无权限』 | EA · groups of 8+ · biweekly · 4 on average | 1/100 |
| 2 | [JP/PvE][BPリサーチ]MatoyServer初しん者〇 | EA · groups of 8+ · biweekly · 2 on average | 1/50 |
| 3 | [JPN] Apple Server | PvP | Vanilla | 2Weekly | EA · groups of 8+ · biweekly · 2 on average | 1/50 |
| 4 | cczsbwd/solo/独狼/原倍半月清/月图/公益服 | EA · no group limit · biweekly · 2 on average | 1/50 |
| 5 | Rustoria.co - SEA Medium | EA · groups of 16+ · biweekly · 77 on average | 133/200 |
Quick answers
From the figures on this page.
Population data
What position does LU测试服 take in the server rankings?
Player hours over the last seven days: #12,902 for LU测试服, #499 in Asia, within the top 60% of the ranked set.
How full does LU测试服 run?
Offline now for LU测试服, with the last sample 13 days 6 hours ago.
About the server
What is the Rust version on LU测试服?
The build is Rust network protocol 2634 and build 167781 on Windows, run by LU测试服. Joining needs the same protocol on your game; Steam handles the update.
Is LU测试服 up, and what does its uptime show?
Offline now for LU测试服, last seen 13 days 6 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 16 October 2026.
In which location is LU测试服 hosted?
With its EA tag, LU测试服 lists itself in Asia. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 1.81.213.251:28015 is its address.
Map and rules
What rules and settings are recorded for LU测试服?
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. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. The VAC field reads off.
Which map has LU测试服 loaded?
LU测试服 runs a procedural map, which the game generates.
Wipes and dates
When does LU测试服 wipe, and on what schedule?
The next wipe for LU测试服 is an estimate, drawn from biweekly: 14 days after its last wipe. Friday 30 October at 09:40 UTC is when the next wipe is due. The world it runs now was generated 13 days 12 hours ago. A fortnightly wipe schedule is published in its tags.
Tags, lists
Which Rust Data filters and lists contain LU测试服?
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.
How should you read the server tags on LU测试服?
The game's server browser reads these tags from LU测试服: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): 100 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): The server runs build 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^b (Biweekly): Wipes run on a two-week cycle; ^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. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
How can I connect to LU测试服?
In Rust, F1 opens the console: type client.connect 1.81.213.251:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.