Offline EA 221.5.40.161:28015 checked 24d ago
LU测试服
Connect
srv = rust.server("221.5.40.161: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 68% of all ranked servers, top 93% 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 14h. # 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.161: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
- 4 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 | [JP] L.R.S.|SOLO|PvP|Beginner|Raid Hours|10/30~11/12 | EA · no group limit · biweekly · 4 on average | 0/? |
| 2 | 瞌睡熊『5倍10废|10.30|萌新首选|无权限』 | EA · groups of 8+ · biweekly · 3 on average | 4/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 | 0/50 |
Quick answers
From the figures on this page.
Population
How does LU测试服 compare in the rankings?
On seven-day player hours LU测试服 is #15,319 overall and #484 in Asia, inside the top 68% of all ranked servers.
How many players does LU测试服 hold at once?
Offline now for LU测试服, with the last sample 24 days 9 hours ago.
Server data
Which Rust version is LU测试服 on?
Rust network protocol 2634 and build 166652 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?
The latest sample has LU测试服 offline, with a last sighting 24 days 9 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 4 October 2026.
Which location does LU测试服 run from?
In Asia, LU测试服 lists itself, using the EA tag. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 221.5.40.161:28015 is its address.
Map and rules
Which rules apply on LU测试服, and what settings?
No gather rate appears in the name: LU测试服. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: 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. 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.
Wipes and dates
On what schedule does LU测试服 wipe?
Expect an estimate: LU测试服's next wipe is projected from biweekly: 14 days after its last wipe. The schedule puts the next wipe on Saturday 31 October at 18:37 UTC. This world was created 26 days 9 hours ago. Its tags carry a wipe schedule of every two weeks.
Lists and tags
Which lists on Rust Data hold LU测试服, and which filters?
On Rust Data, LU测试服 appears in these lists: 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.
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): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^b (Biweekly): Wipes run on a two-week cycle; ^o (Oxide): Plugin framework: Oxide (uMod); ^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. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
How can I connect to LU测试服?
In Rust, F1 opens the console: type client.connect 221.5.40.161:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.