RUST METRICSFlight deck · live data
Data live Servers11,765 Players73,690 Populated3,473 Fresh wipes 3 h215 Scan5 min
‹ All servers15.235.180.140:21015
Offline Full Queue Fresh wipe Wipe due No query

测试测试

Offline 15.235.180.140:21015 checked 23d 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,946top 71%
Last wipe23d 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
15k10k15k20k6 Oct7 Oct9 Oct10 Oct12 Oct13 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

How often does 测试测试 wipe, and when?

The rhythm of 测试测试's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 23 days 16 hours ago the current world was made.

Lists and filters

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

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): 100 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166652 (Build): Game build reading: 166652; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game from 测试测试. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

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

Rust Metrics lists featuring 测试测试: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Occupancy

Where does 测试测试 sit in the rankings?

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

How full does 测试测试 get?

Status for 测试测试: offline. Last seen 23 days 16 hours ago.

Server

What location is 测试测试 hosted in?

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. Check: address. It reads 15.235.180.140:21015.

What Rust version is 测试测试 on?

Version check: Rust network protocol 2634 and build 166652 on Windows, run by 测试测试. Check: protocol. To join, your game must match; Steam handles the update.

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

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

Settings and map

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

No gather rate appears in the name: 测试测试. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.

What map is 测试测试 on?

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

Join

How can you get onto 测试测试?

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

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players 100 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166652
Build Game build reading: 166652.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^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.