Working its way up from the back of the class: #16,020 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
53/ 100
D
Moving up: up 877 places this week.
A term to build on.
Strongest in momentum (D); standing is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
No daily history yet.
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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
RankRank in region
Top 71% of all ranked servers, top 93% in EA. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Next wipe Saturday 31 October, 17:20 UTC, in 1d 23h.
Biweekly: 14 days after its last wipe
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
classmates: the same kind of game, then region, group limit, rate and wipes
The EA tag on LU测试服 puts it in Asia. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 221.5.41.6:28015 is the address to use.
Is LU测试服 up, and how steady is its uptime?
You cannot join now: LU测试服 is offline, last seen 25 days 23 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 3 October 2026.
Which Rust version is LU测试服 running?
The server LU测试服 is on Rust network protocol 2634 and build 166652 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does LU测试服 reset?
The next wipe on LU测试服 is a projection from biweekly: 14 days after its last wipe. Saturday 31 October at 17:20 UTC is the date set for its next wipe. The world it runs now was created 26 days. Its tags say it wipes every two weeks.
Player numbers
Where does LU测试服 place in the wider field of Rust servers?
Over the last seven days, LU测试服 has #16,020 for player hours, in the top 71% of all ranked servers and #487 in Asia.
How many players does LU测试服 usually have?
LU测试服 is offline at the moment; the last time it was seen was 25 days 23 hours ago.
Tags
How should you read the tags on LU测试服?
gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): Its slot count is 100; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166652 (Build): The game build is 166652; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^b (Biweekly): A wipe happens once a fortnight; ^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 appears under East Asia are the tags LU测试服 publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature LU测试服?
These Rust Server Score lists count LU测试服 among them: Modded Rust servers, graded. It shows under the following 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.
Server rules
What settings and rules apply on LU测试服?
You will find no gather rate in the name of LU测试服. The default of 8 players applies as the group cap. You get survival here, gather and build and raid: the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. VAC, Valve's anti-cheat, is not enabled.
Can you tell me which map LU测试服 uses?
A procedural map, generated by the game, is what LU测试服 runs.
How to join
What is the way to join LU测试服?
Enter client.connect 221.5.41.6:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,^b,EA,gmrust,cs166652,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp100
Max playersIts slot count is 100.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166652
BuildThe game build is 166652.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^b
BiweeklyA wipe happens once a fortnight.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
Region
EA
East AsiaIn the server browser it appears under East Asia.
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.
A term to build on. Strongest in momentum (D); standing is the one to work on (F).