RUST METRICSFlight deck · live data
Data live Servers11,720 Players60,549 Populated3,378 Fresh wipes 3 h181 Scan5 min
‹ All servers1.81.214.47:28015
Offline Full Queue Fresh wipe Wipe due No query

LU测试服

Offline EA 1.81.214.47:28015 checked 42d ago

biweekly wipes moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 0 /100

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,497#479 in EA
Last wipe42d agobiweekly schedule
Next wipe7d 7hThu 5 Nov, 19:00 UTC FW
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep21 Sep22 Sep23 Sep
PLAN

Wipe schedule

Next wipe Thursday 5 November, 19:00 UTC, in 7d 7h. The force wipe

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

When does LU测试服 wipe?

An estimate from the force wipe gives LU测试服's next wipe. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. The world it runs now was made 42 days 23 hours ago. The tags carry an every-two-weeks wipe schedule.

Tags

How should you read the tags on LU测试服?

Tags published by LU测试服, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163794 (Build): The server runs game build 163794; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^b (Biweekly): Two-week wipe schedule; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Plugins or settings make this a modded server; EA (East Asia): The server browser files it under East Asia. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does LU测试服 appear in Rust Metrics lists and filters?

On Rust Metrics, LU测试服 sits in these lists: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Region: Asia; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.

Player count

What position does LU测试服 hold among Rust servers?

Top – of all ranked servers: LU测试服 takes #15,497 on seven-day player hours and #479 in Asia.

What is the population on LU测试服?

Status for LU测试服: offline. Last seen 42 days 21 hours ago.

Server

Which location does LU测试服 run from?

Reading: location. The EA tag puts LU测试服 in Asia. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 1.81.214.47:28015.

What Rust version is LU测试服 on?

Rust network protocol 2633 and build 163794 on Windows is the build LU测试服 runs. To get in, your game needs the same protocol; Steam applies the update.

Is LU测试服 up, and how often does it stay up?

Check: connection. LU测试服 is offline at this moment. Last contact was 42 days 21 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 16 September 2026.

Settings and map

How is LU测试服 configured, and what rules are in force?

No gather rate appears in the name: LU测试服. The group cap is 8 players, which is the default in the game. Mode check gives survival; gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is off.

Which map is live on LU测试服?

The game generates a procedural map for LU测试服.

Join

How do you connect to LU测试服?

Check: join. Open Rust, press F1, then enter client.connect 1.81.214.47:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2633,^b,EA,gmrust,cs163794,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players The server holds 100 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Protocol 2633: join only on the same game version.
cs163794
Build The server runs game build 163794.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

Wipe schedule

^b
Biweekly Two-week wipe schedule.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Plugins or settings make this a modded server.

Region

EA
East Asia The server browser files it 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.