RUST METRICSFlight deck · live data
Data live Servers11,742 Players66,506 Populated3,391 Fresh wipes 3 h202 Scan5 min
‹ All servers39.144.114.141:20000
Offline Full Queue Fresh wipe Wipe due No query

测试测试

Offline 39.144.114.141:20000 checked 27d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 10 20 30 40 PAX 0 /40

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,920top 70%
Last wipe57d agono schedule published
Next wipe–no wipe seen yet
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
15k10k15k20k25 Sep28 Sep1 Oct3 Oct6 Oct9 Oct

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

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly 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 测试测试 wipe?

Its rhythm cannot be told from the wipes of 测试测试 on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 57 days ago.

Tags

Which tags does 测试测试 carry, and what do they mean?

Tags published by 测试测试, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp40 (Max players): 40 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2632 (Protocol): Protocol 2632: join only on the same game version; cs162434 (Build): Game build reading: 162434; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. 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 测试测试?

These Rust Metrics lists carry 测试测试: Rust community servers: live readings. Check: filters. On the server list it appears under these: Region: Asia; Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

Where does 测试测试 sit in the rankings?

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

What player count does 测试测试 carry?

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

Operator and location

Where does 测试测试 sit?

Check: location. No region tag comes from 测试测试, but the name points to Asia. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 39.144.114.141:20000.

What Rust version is 测试测试 on?

Reading: 测试测试, Rust network protocol 2632 and build 162434, Linux. Matching protocol is required to join. Let Steam update your game.

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

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

Settings and map

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

No gather rate appears in the name: 测试测试. 8 players per group, the default value. Mode check gives survival; gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.

What map is 测试测试 on?

Check: map. Procedural, generated by the game, on 测试测试.

Connection

How can you get onto 测试测试?

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

PLACARDS

Server tags

what each one means

Published as mp40,ptrak,$r?,v2632,gmrust,cs162434,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp40
Max players 40 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2632
Protocol Protocol 2632: join only on the same game version.
cs162434
Build Game build reading: 162434.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

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.