RUST METRICSFlight deck · live data
Data live Servers11,892 Players102,135 Populated3,937 Fresh wipes 3 h401 Scan5 min
‹ All servers202.189.11.108:10040
Online Full Queue Fresh wipe Wipe due No query

测试

Online EA 202.189.11.108:10040 checked 12m ago

monthly wipes vanillaoxide
COM 1 · connect

Server instruments

last reading Thu 16:00 UTC
0 25 50 75 100 PAX 1 /100

Players now

1% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 33 SERVER FPS

Server fps

48 h low 33 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 116,911 ×1000

Entities

48 h range 116,645–120,310 · memory 3,146 MB
1239 ET SINCE RESTART 10:58

Uptime

10 h 58 min since its last restart, at the last reading
7-day average4peak 18
Rank#1,524top 7% · #153 in EA
Last wipe6d agomonthly schedule
Next wipe7d 1hThu 5 Nov, 19:00 UTC FW
Memory3,146MB48 h peak 6 players
REC 1

Players

AveragePeak
0246818:0001:0009:0016:0009:0016:00

Hourly average and peak, UTC.

REC 2

Server performance

02040608018:0001:0009:0016:0009:0016:00

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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
11k2k3k4k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 7% of all ranked servers, top 28% in EA. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

force wipes only

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

usual gap7 daysbetween real wipes
on rhythm60%of its recent wipes
wipe-day peak17players, last three wipes
crowd held20%else halves by day 4

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC7d 1hFW
  2. WPT 2Thu 3 Dec, 19:00 UTC35d 1hFW

The first 48 hours of its last wipes

Fri 23 OctTue 20 OctThu 8 Oct
05101520+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 18, 32 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 23 Oct, 05:39 UTC6d ago 18 – running 3
Tue 20 Oct, 00:07 UTC9d ago 20 held half 3.2 days 0
Thu 8 Oct, 23:30 UTC20d ago 14 halved by day 3 11 days 0
Thu 1 Oct, 23:57 UTC FW27d ago 17 halved by day 5 7 days 0
Fri 25 Sep, 00:18 UTC34d ago 20 halved by day 3 7 days 2
Thu 17 Sep, 23:29 UTC41d ago 18 halved by day 6 7 days 0

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 timing

What happens on 测试 when wipe day comes?

The busiest point of its recent wipes drew 17 players on average. 32 hours after the wipe, the crowd peaked on the latest wipe. The crowd stayed above half that peak until the next wipe in 20% of its recent wipes. When it didn't hold, by day 4 it fell below half.

What wipe timing does 测试 follow?

Once a month 测试 wipes, with the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world it runs now was made 6 days 11 hours ago. A monthly wipe schedule is published in its tags.

Tags

How should you read the tags on 测试?

Tags published by 测试, read by the game's server browser: gmvanilla (Game mode): Check: mode. Vanilla survival; mp100 (Max players): The server holds 100 slots; ts6 (Group limit): Team cap: 6; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^m (Monthly): Facepunch's force wipe sets the monthly cycle here; ^v (Vanilla): Unmodified from Facepunch's release: no altered rates, no kits, no extra rules; ^o (Oxide): It runs Oxide, also known as uMod; EA (East Asia): The server browser files it under East Asia. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

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

On Rust Metrics, 测试 sits in these lists: Rust community servers: live readings and Vanilla Rust servers, live. Check: filters. On the server list it appears under these: Region: Asia; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Monthly ^m, Vanilla ^v and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last week.

Population

What position does 测试 hold among Rust servers?

Player hours over the last seven days put 测试 at #1,524, #153 in Asia, in the top 7% of all ranked servers.

What is the population on 测试?

1 of 100 slots are filled on 测试 right now. Check: players over seven days. Average 4, peak 18. The last 48 hours peaked at 01:00 UTC, averaging 5 players at that hour.

Operator and location

What location is 测试 hosted in?

Reading: location. The EA tag puts 测试 in Asia. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 202.189.11.108:10040.

What Rust version is 测试 on?

Version check: Rust network protocol 2635 and build 168909 on Windows, run by 测试. Check: protocol. To join, your game must match; Steam handles the update.

What is the performance reading for 测试?

Over the last 48 hours the average was 50 server fps; the floor was 33. Reading: 120,310 entities at the highest. That covers buildings, deployables and everything else. Check: memory. Peak use was 4,218 MB. Lag, as players feel it, is low fps plus a climbing entity count.

How reliable is 测试, and is it online now?

Check: connection. 测试 is online at this moment. Check: restart. The uptime it reports puts the last restart about 10 hours ago. Uptime for the last 7 full days: 162 of 168 hours, or 96%. The first sighting on Rust Metrics was 17 September 2026.

Settings and map

What settings and rules apply on 测试?

No gather rate appears in the name: 测试. The cap on groups is 6 players. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. The server browser lists it under Community. Plugin count: Oxide. The server calls itself vanilla, with this meaning: unmodified from Facepunch's release: no altered rates, no kits, no extra rules. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on 测试?

Check: map. Procedural, size 4,250, seed 1482314174, generated by the game on 测试. The map repeats when size and seed match. Open it on RustMaps from this page.

Join

How can you get onto 测试?

Press F1 in Rust and enter client.connect 202.189.11.108:10040. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,^m,^v,EA,gmvanilla,cs168909,ts6,^o

Game

gmvanilla
Game mode Check: mode. Vanilla survival.
mp100
Max players The server holds 100 slots.
ts6
Group limit Team cap: 6.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Wipe schedule

^m
Monthly Facepunch's force wipe sets the monthly cycle here.

Difficulty

^v
Vanilla Unmodified from Facepunch's release: no altered rates, no kits, no extra rules.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.

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.