测试测试
Offline 39.144.114.131:20000 checked 19d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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.
Rank
daily · 1 is bestTop 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 133/200
- 0/550
- 26/200
- 48/100
- 2/200
- 28/150
Quick answers
from the figures on this pageWipe schedule
What wipe timing does 测试测试 follow?
The rhythm of 测试测试's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 57 days ago.
Tags
How should you read the tags on 测试测试?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp40 (Max players): 40 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2632 (Protocol): Protocol 2632: join only on the same game version; cs162434 (Build): The server runs game build 162434; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set from 测试测试. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does 测试测试 appear in Rust Metrics lists and filters?
On Rust Metrics, 测试测试 sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Region: Asia; Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Occupancy
Where does 测试测试 sit in the rankings?
Ranking for 测试测试: #15,858 on seven-day player hours, top 72% of all ranked servers.
What is the population on 测试测试?
Status for 测试测试: offline. Last seen 19 days ago.
Server details
What location is 测试测试 hosted in?
The name of 测试测试 points to Asia, though it publishes no region tag. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 39.144.114.131:20000.
What Rust version is 测试测试 on?
Rust network protocol 2632 and build 162434 on Linux is the build 测试测试 runs. 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 19 days ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 10 October 2026, recorded by Rust Metrics.
Rules and settings
What rules does 测试测试 enforce, and what are its settings?
Check: gather rate. The name 测试测试 does not state one. No limit is set beyond the default. Groups take up to 8 players. survival, the normal game: build, gather, raid — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on 测试测试?
The game generates a procedural map for 测试测试.
Connection
How can you get onto 测试测试?
Press F1 in Rust and enter client.connect 39.144.114.131:20000. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.