Not ranked yet, so there is no place in the school to report.
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
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
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
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 Thursday 5 November, 19:00 UTC, in 7d 3h.
The force 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. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 1.81.213.159:28015.
How reliable is LU测试服, and is it up?
The server is down: LU测试服 is offline now, with the last sighting 42 days 1 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 17 September 2026.
What Rust version is LU测试服 on?
The server LU测试服 is on Rust network protocol 2633 and build 163794 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
When does LU测试服 wipe, and how often?
the force wipe gives the basis for estimating LU测试服's next wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. The world it runs now was created 42 days 14 hours. Its tags give a wipe schedule of every two weeks.
Player count
Where does LU测试服 sit among Rust servers?
In Asia, LU测试服 is #461, and overall it is #13,296 on player hours over the last seven days, in the top – of all ranked servers.
How many players does LU测试服 usually have?
LU测试服 is offline at the moment; the last time it was seen was 42 days 1 hours ago.
Tags and filters
What is meant by the tags on LU测试服?
The game's browser takes its cue from the tags LU测试服 has set: gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): Its slot count is 100; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs163794 (Build): The game build is 163794; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^b (Biweekly): The server wipes on a two-week cycle; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; EA (East Asia): In the server browser it appears under East Asia. At the top of the page you'll see the live player count, the queue and the world's age, taken from the 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.
Map and rules
Which rules does LU测试服 enforce, and what are its settings?
You will find no gather rate in the name of LU测试服. The default of 8 players applies as the group cap. It runs survival, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. VAC, Valve's anti-cheat, is not enabled.
LU测试服 runs which map?
The game generates a procedural map for LU测试服.
Connecting
How do you get onto LU测试服?
To connect, start Rust, press F1, and type client.connect 1.81.213.159:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2633,^b,EA,gmrust,cs163794,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max playersIts slot count is 100.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs163794
BuildThe game build is 163794.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Wipe schedule
^b
BiweeklyThe server wipes on a two-week cycle.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedThe game is changed by plugins or settings; you will find it 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.
Not enough figures yet to write a report. Check back after a few days on the list.