RUST METRICSFlight deck · live data
Data live Servers11,842 Players74,292 Populated3,699 Fresh wipes 3 h224 Scan5 min
‹ All servers1.81.212.187:28015
Offline Full Queue Fresh wipe Wipe due No query

LU测试服

Offline EA 1.81.212.187:28015 checked 41d ago

biweekly wipes moddedoxide
COM 1 · connect

Server instruments

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

Players now

1% 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#13,268#461 in EA
Last wipe42d agobiweekly schedule
Next wipe7d 5hThu 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 Sep24 Sep25 Sep
PLAN

Wipe schedule

Next wipe Thursday 5 November, 19:00 UTC, in 7d 5h. 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

Reset cycle

What wipe timing does LU测试服 follow?

From the force wipe, the next wipe of LU测试服 is an estimate. 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 12 hours ago. A wipe schedule of every two weeks is published in its tags.

Tags

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

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): Slots: 100; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163794 (Build): Build 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^b (Biweekly): Two-week wipe schedule; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; EA (East Asia): Its browser listing: East Asia from LU测试服. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

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

Rust Metrics lists featuring LU测试服: 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.

Population

Where does LU测试服 sit in the rankings?

Player hours over the last seven days put LU测试服 at #13,268, #461 in Asia, in the top – of all ranked servers.

What player count does LU测试服 carry?

Status for LU测试服: offline. Last seen 41 days 11 hours ago.

Server

What location is LU测试服 hosted in?

Its EA tag places 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.212.187:28015.

What Rust version is LU测试服 on?

Version check: Rust network protocol 2633 and build 163794 on Windows, run by LU测试服. Matching protocol is required to join. Let Steam update your game.

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

Check: connection. LU测试服 is offline at this moment. Last contact was 41 days 11 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 18 September 2026.

Rules and settings

What settings and rules apply on LU测试服?

No gather rate appears in the name: LU测试服. The group cap is 8 players, which is the default in the game. survival, the normal game: build, gather, raid — that is the game mode. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is off.

Which map is live on LU测试服?

Procedural map on LU测试服, made by the game's generator.

Join

How do you connect to LU测试服?

Check: join. Open Rust, press F1, then enter client.connect 1.81.212.187: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 Slots: 100.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Match the game version: protocol 2633 is required.
cs163794
Build Build 163794.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Wipe schedule

^b
Biweekly Two-week wipe schedule.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Check: category. Modded, because plugins or settings alter the game.

Region

EA
East Asia Its browser listing: 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.