RUST METRICSFlight deck · live data
Data live Servers11,800 Players73,970 Populated3,706 Fresh wipes 3 h107 Scan5 min
‹ All servers111.85.241.22:28015
Offline Full Queue Fresh wipe Wipe due No query

测试

Offline 111.85.241.22:28015 checked 35d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 0 /100

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,460top 71%
Last wipe35d 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
15k10k15k20k23 Sep24 Sep26 Sep27 Sep29 Sep30 Sep

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

When does 测试 wipe?

To tell the rhythm of 测试, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 35 days 9 hours ago the current world was made.

Lists and filters

How should you read the tags on 测试?

These are the tags 测试 publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): Slots: 100; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): Build 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show 测试?

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

Player count

What position does 测试 hold among Rust servers?

Ranking for 测试: #15,460 on seven-day player hours, top 71% of all ranked servers.

What player count does 测试 carry?

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

Server

Where does 测试 sit?

Check: location. No region tag comes from 测试, but the name points to Asia. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 111.85.241.22:28015.

What Rust version is 测试 on?

Reading: 测试, Rust network protocol 2633 and build 165217, Windows. Check: protocol. To join, your game must match; Steam handles the update.

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

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

Settings and map

What settings and rules apply on 测试?

No gather rate appears in the name: 测试. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; gather, build and raid, as the game normally runs. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on 测试?

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

How to join

What do you do to join 测试?

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp100
Max players Slots: 100.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build Build 165217.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is 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.