测试测试
Offline 39.144.114.129:20000 checked 18d 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- 169/200
- 2/550
- 35/200
- 62/125
- 0/200
- 35/150
Quick answers
from the figures on this pageReset cycle
What wipe timing does 测试测试 follow?
The rhythm of 测试测试's wipes cannot be told yet: too few are on record. 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 56 days 22 hours 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): Slots: 40; 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): Build 162434; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set 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 测试测试: 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?
Player hours over seven days put 测试测试 at #15,849, in the top 72% of all ranked servers.
How full does 测试测试 get?
Reading for 测试测试: offline at this moment; last seen 18 days 22 hours ago.
Server
Where does 测试测试 sit?
The name of 测试测试 points to Asia, though it publishes no region tag. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 39.144.114.129:20000.
What Rust version is 测试测试 on?
Version check: Rust network protocol 2632 and build 162434 on Linux, 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 18 days 22 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 8 October 2026.
Rules and settings
What settings and rules apply on 测试测试?
Reading the name gives no gather rate for 测试测试. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Listing: Community server. VAC is on. That is Valve's anti-cheat.
What map is 测试测试 on?
Procedural map on 测试测试, made by the game's generator.
How to join
How can you get onto 测试测试?
Check: join. Open Rust, press F1, then enter client.connect 39.144.114.129:20000. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.