RUST METRICSFlight deck · live data
Data live Servers11,856 Players101,030 Populated3,903 Fresh wipes 3 h542 Scan5 min
‹ All servers125.118.193.126:40000
Offline Full Queue Fresh wipe Wipe due No query

测试1

Offline 125.118.193.126:40000 checked 31d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 0 /1

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#16,960top 71%
Last wipe31d 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
15k10k15k20k28 Sep29 Sep1 Oct2 Oct4 Oct5 Oct

Top 71% 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

What wipe timing does 测试1 follow?

Its rhythm cannot be told from the wipes of 测试1 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 31 days 6 hours ago.

Tag meanings

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

These are the tags 测试1 publishes, and the server browser reads them: gmvanilla (Game mode): Survival on vanilla settings; mp1 (Max players): 1 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): Build 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

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

These Rust Metrics lists carry 测试1: 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.

Occupancy

What position does 测试1 hold among Rust servers?

Player hours over seven days put 测试1 at #16,960, in the top 71% of all ranked servers.

What player count does 测试1 carry?

Reading for 测试1: offline at this moment; last seen 31 days 6 hours ago.

Server details

What location is 测试1 hosted in?

Reading: location. Nothing in the tags, but the name of 测试1 points to Asia. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 125.118.193.126:40000.

What Rust version is 测试1 on?

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

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

Check: connection. 测试1 is offline at this moment. Last contact was 31 days 6 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 28 September 2026.

Settings and map

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

Check: gather rate. The name 测试1 does not state one. 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. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

What map is 测试1 on?

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

How to join

What do you do to join 测试1?

Press F1 in Rust and enter client.connect 125.118.193.126:40000. 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 mp1,ptrak,$r?,v2633,gmvanilla,cs165217,ts8

Game

gmvanilla
Game mode Survival on vanilla settings.
mp1
Max players 1 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Protocol 2633: join only on the same game version.
cs165217
Build Build 165217.
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.