RUST METRICSFlight deck · live data
Data live Servers11,805 Players79,944 Populated3,786 Fresh wipes 3 h105 Scan5 min
‹ All servers47.110.181.82:28015
Offline Full Queue Fresh wipe Wipe due No query

测试

Offline 47.110.181.82:28015 checked 8d ago

biweekly wipes
COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

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,351top 70%
Last wipe8d agobiweekly schedule
Next wipe5d 13hTue 3 Nov, 09:51 UTC
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 Oct21 Oct23 Oct24 Oct26 Oct27 Oct

Top 70% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

Next wipe Tuesday 3 November, 09:51 UTC, in 5d 13h. Biweekly: 14 days after its last 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

How often does 测试 wipe, and when?

The estimate for 测试's next wipe comes from biweekly: 14 days after its last wipe. Due on Tuesday 3 November at 09:51 UTC is its next wipe. The world in play was created 8 days 10 hours ago. A wipe schedule of every two weeks is published in its tags.

Lists and filters

How should you read the tags on 测试?

These are the tags 测试 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): 50 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): Build 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^b (Biweekly): Check: wipe cycle. Every two weeks. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show 测试?

On Rust Metrics, 测试 sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Region: Asia; Type: Community (not modded, not official) and No plugins at all; Server tag: Biweekly ^b; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.

Population

Where does 测试 sit in the rankings?

Player hours over seven days put 测试 at #15,351, in the top 70% of all ranked servers.

What is the population on 测试?

Reading for 测试: offline at this moment; last seen 8 days 10 hours ago.

Operator and location

What location is 测试 hosted in?

The name of 测试 points to Asia, though it publishes no region tag. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 47.110.181.82:28015.

What Rust version is 测试 on?

Reading: 测试, Rust network protocol 2634 and build 167781, Windows. Matching protocol is required to join. Let Steam update your game.

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

Check: connection. 测试 is offline at this moment. Last contact was 8 days 10 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 20 October 2026, recorded by Rust Metrics.

Settings and map

What rules does 测试 enforce, and what are its settings?

Check: gather rate. The name 测试 does not state one. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is off.

What map is 测试 on?

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

How to join

What do you do to join 测试?

To join: start Rust, press F1 and type client.connect 47.110.181.82:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2634,^b,gmrust,cs167781,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players 50 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167781
Build Build 167781.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

Wipe schedule

^b
Biweekly Check: wipe cycle. Every two weeks.

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.