LU测试服
Key statistics
the figures behind the quote- Players now
- 0/ 100 0% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #15,319 top 68% · #484 in EA
- Rank · 7d ago
- #12,697 ▼2622 places down
- Last wipe
- 11d ago biweekly schedule
- Next wipe
- 2d 12h Sat 17 Oct, 18:37 UTC
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 0 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 4 Oct 2026 no hostname published
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 68% of all ranked servers, top 93% in EA. Ranked on player hours over the last seven days.
Wipe schedule
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | ［JP］初心者PVPサーバー｜RaidTime・ EventsEA · groups of 10+ · biweekly · 5 on average | 2/100 | ▲+2 | |
| 2 | 瞌睡熊『5倍10废|10.15|萌新首选|无权限』EA · groups of 8+ · biweekly · 3 on average | 3/100 | ▲+1+50.0% | |
| 3 | [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/2~10/15EA · no group limit · biweekly · 3 on average | 0/20 | ▼−2−100.0% | |
| 4 | cczsbwd/solo/独狼/原倍半月清/月图/公益服EA · no group limit · biweekly · 2 on average | 0/50 | ▼−1−100.0% | |
| 5 | [JP/PvE][BPリサーチ]MatoyServer初しん者〇EA · groups of 8+ · biweekly · 1 on average | 0/50 | ▪+0 | |
| 6 | Rustoria.co - SEA MediumEA · groups of 16+ · biweekly · 46 on average | 32/200 | ▲+2+7.0% |
Quick answers
from the figures on this pageRules & Settings
What settings and rules are in place on LU测试服?
No gather rate is given in the name of LU测试服. Groups can contain a maximum of 8 players, the default for the game. It runs survival, gather, build and raid in the standard game. You can fight and raid other players. Modded is its category in the server browser; plugins or settings modify the game. Oxide plugins are in use. VAC, Valve's anti-cheat, is disabled.
Which map is played on LU测试服?
A procedural map runs on LU测试服, created by the game.
Player Count
What is the rank of LU测试服?
On seven-day player hours, LU测试服 sits at #15,319, in the top 68% across ranked servers and #484 in Asia.
What is the population on LU测试服?
Right now, LU测试服 is offline; the last sighting was 9 days 11 hours ago.
Wipe Schedule
When does LU测试服 schedule its wipes?
From biweekly: 14 days after its last wipe, the next wipe at LU测试服 is estimated. The date of its next wipe is Saturday 17 October at 18:37 UTC. Its world now is 11 days 11 hours old. A fortnightly wipe is published in its tags.
Server Details
Where can LU测试服 be found?
With the EA tag, LU测试服 lists itself in Asia. Rust Analytics reports the location a server claims, not the machine's actual location. You can reach it at 221.5.40.161:28015.
LU测试服 is on which Rust version?
The build is Rust network protocol 2634 and build 166652 on Windows, running on LU测试服. Joining requires the same protocol on your game, which Steam updates.
Is LU测试服 up, and how consistent is its uptime?
No response from LU测试服. It was last seen 9 days 11 hours ago. 7 full days have passed with 0% uptime, 0 of 168 hours. The earliest Rust Analytics saw it was 4 October 2026.
Server Tags
How should you interpret the tags on LU测试服?
Published by LU测试服 for the game's server browser to read: gmrust (Game mode): Survival in the standard Rust format; mp100 (Max players): It holds 100 slots; ts8 (Group limit): 8 per team: the default setting, unchanged; v2634 (Protocol): To join, your game needs protocol 2634; cs166652 (Build): Game build: 166652; ptrak (Networking): Runs on RakNet, Rust's default network layer; $r? (Region code): The region code is absent; ^b (Biweekly): One wipe every fortnight; ^o (Oxide): The plugin framework Oxide (uMod) is in use; ^z (Modded): The Modded listing applies: plugins or settings change play; EA (East Asia): The browser places this server in East Asia. The tags also carry its current players, queue and world creation time; this page shows them at the top.
Where does LU测试服 show up in Rust Analytics lists and filters?
On Rust Analytics, LU测试服 matches 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 to Join
How can I connect to LU测试服?
The console route: start Rust, press F1, enter client.connect 221.5.40.161:28015. The page's Launch Rust button opens Rust through Steam and connects you instead.
Server tags
what each one meansPublished as mp100,ptrak,$r?,v2634,^b,EA,gmrust,cs166652,ts8,^o^z
Game
gmrust
mp100
ts8
v2634
cs166652
ptrak
$r?
Wipe schedule
^b
Mods and access
^o
^z
Region
EA
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.