Offline EA 221.5.40.173:28015 checked 23d ago
LU测试服
Connect
srv = rust.server("221.5.40.173: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 61% of all ranked servers, top 90% in EA. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Next wipe Saturday 31 October, 18:37 UTC, in 1d 16h. # 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
- 221.5.40.173:28015
- region
- EA
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- biweekly
- last wipe
- 3 Oct 2026, 18:37 UTC
- hostname
- –
- first seen
- 3 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 | 2/100 |
| 2 | [JP/PvE][BPリサーチ]MatoyServer初しん者〇 | EA · groups of 8+ · biweekly · 2 on average | 0/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 · 78 on average | 77/200 |
Quick answers
From the figures on this page.
Player counts
How does LU测试服 compare in the rankings?
On seven-day player hours LU测试服 is #13,782 overall and #475 in Asia, inside the top 61% of all ranked servers.
How many players does LU测试服 hold at once?
LU测试服 returns no live count at this refresh, having last been seen 23 days 15 hours ago.
Server facts
Which Rust version is LU测试服 on?
The build is Rust network protocol 2634 and build 166652 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 23 days 15 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 3 October 2026.
Where does LU测试服 sit?
With its EA tag, LU测试服 lists itself in Asia. 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 221.5.40.173:28015.
Settings and map
Which settings and rules does LU测试服 run?
No gather rate appears in the name: LU测试服. The group limit sits at the default of 8 players. Recorded as survival, the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. VAC is not running; Valve's anti-cheat is off.
What is the map on LU测试服?
LU测试服 runs a procedural map, which the game generates.
Wipe schedule
On what schedule does LU测试服 wipe?
The next wipe for LU测试服 is an estimate, drawn from biweekly: 14 days after its last wipe. Saturday 31 October at 18:37 UTC is when the next wipe is due. The world it runs now was generated 26 days 7 hours ago. A fortnightly wipe schedule is published in its tags.
Tags and filters
Where does LU测试服 appear among Rust Data lists and filters?
The Rust Data lists that LU测试服 fits are: Modded Rust servers. These filters bring it up 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测试服?
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; cs166652 (Build): Build number: 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^b (Biweekly): Wipes run on a two-week cycle; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings; 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 221.5.40.173:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.