On the class lists: F (31), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average0peak –
Rank#15,400top 69% · #500 in EA
Last wipe3d agobiweekly schedule
Next wipe8d 21hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 100 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,400 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
unmarked
–
No rank a week ago to compare with.
A term to build on.
Strongest in standing (F); population 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 69% of all ranked servers, top 91% 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 Thursday 5 November, 19:00 UTC, in 8d 21h.
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
In Asia, according to its own listing, sits LU测试服, with the EA tag. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 58.255.236.175:28015.
Is LU测试服 up, and how steady is its uptime?
You cannot join now: LU测试服 is offline, last seen 3 days 10 hours ago. It was up 0 of 48 hours over the last 2 full days, which is 0% of the time. The first sighting by Rust Server Score was on 24 October 2026.
On what Rust version does LU测试服 sit?
Rust network protocol 2635 and build 168909 on Windows is what LU测试服 runs. Steam updates your game for you, but you need the same protocol to join.
Resets
On what schedule does LU测试服 reset?
The estimate for LU测试服's next wipe comes from the force wipe. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. 3 days 12 hours have passed since this world was made. Its tags say it wipes every two weeks.
Player numbers
Where does LU测试服 sit among Rust servers?
In Asia, LU测试服 is #500, and overall it is #15,400 on player hours over the last seven days, in the top 69% of all ranked servers.
How many players does LU测试服 usually have?
It has been 3 days 10 hours since LU测试服 was last seen, and it is offline right now. A seven-day average of 0 players applies here.
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): This one runs plain Rust survival, with nothing altered; mp100 (Max players): 100 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^b (Biweekly): A wipe happens once a fortnight; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; EA (East Asia): You will find it under East Asia in the browser. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does LU测试服 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count LU测试服 among them: Modded Rust servers, graded. You can find it under these server-list filters: 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 week.
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. survival is the mode here, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. The server does not run VAC, Valve's anti-cheat.
LU测试服 runs which map?
The game generates a procedural map for LU测试服.
Getting in
What is the way to join LU测试服?
To connect, start Rust, press F1, and type client.connect 58.255.236.175:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,^b,EA,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp100
Max players100 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Wipe schedule
^b
BiweeklyA wipe happens once a fortnight.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
Region
EA
East AsiaYou will find it under East Asia in the browser.
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 standing (F); population is the one to work on (F).