RUST METRICSFlight deck · live data
Data live Servers11,819 Players71,592 Populated3,741 Fresh wipes 3 h139 Scan5 min
‹ All servers106.45.4.56:28015
Offline Full Queue Fresh wipe Wipe due No query

测试

Offline 106.45.4.56:28015 checked 29d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 4 8 11 15 PAX 1 /15

Players now

7% 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,491top 69%
Last wipe29d agono schedule published
Next wipe–too few wipes 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 69% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 4 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 28 Sep, 03:33 UTC29d ago 1 – running 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 schedule

What should you expect from wipe day on 测试?

The busiest point of its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 4 hours.

What wipe timing does 测试 follow?

Its rhythm cannot be told from the wipes of 测试 on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 29 days 17 hours ago.

Tags

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; mp15 (Max players): The server holds 15 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): Game build reading: 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

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

On Rust Metrics, 测试 sits in these lists: Modded Rust servers, checked live. Reading: server list filters. It comes up under Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Population

What position does 测试 hold among Rust servers?

Ranking for 测试: #16,491 on seven-day player hours, top 69% of all ranked servers.

What player count does 测试 carry?

测试 is not responding; status offline, last seen 29 days 14 hours ago.

Server

What location is 测试 hosted in?

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 106.45.4.56:28015.

What Rust version is 测试 on?

Rust network protocol 2633 and build 165217 on Windows is the build 测试 runs. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on 测试, and is it online?

测试 reports offline. The last reading came 29 days 14 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 28 September 2026.

Rules and settings

What settings and rules apply on 测试?

Check: gather rate. The name 测试 does not state one. No limit is set beyond the default. Groups take up to 8 players. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

What map is 测试 on?

The game generates a procedural map for 测试.

Connection

How do you connect to 测试?

Press F1 in Rust and enter client.connect 106.45.4.56:28015. 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 mp15,ptrak,$r?,v2633,gmrust,cs165217,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp15
Max players The server holds 15 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Match the game version: protocol 2633 is required.
cs165217
Build Game build reading: 165217.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Mods and access

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

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.