测试测试
Offline 39.144.114.143:20000 checked 34d 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 71% 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- 137/200
- 1/550
- 31/200
- 47/225
- 0/200
- 28/150
Quick answers
from the figures on this pageReset cycle
How often does 测试测试 wipe, and when?
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 in play was created 56 days 23 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; mp40 (Max players): The server holds 40 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2632 (Protocol): Your game must run protocol 2632 to get in; cs162434 (Build): The server runs game build 162434; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. 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?
These Rust Metrics lists carry 测试测试: 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
What position does 测试测试 hold among Rust servers?
Player hours over seven days put 测试测试 at #16,434, in the top 71% of all ranked servers.
What player count does 测试测试 carry?
Reading for 测试测试: offline at this moment; last seen 34 days 5 hours ago.
Server details
What location is 测试测试 hosted in?
Reading: location. Nothing in the tags, but the name of 测试测试 points to Asia. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 39.144.114.143:20000.
What Rust version is 测试测试 on?
Version check: Rust network protocol 2632 and build 162434 on Linux, run by 测试测试. To get in, your game needs the same protocol; Steam applies the update.
Is 测试测试 up, and how often does it stay up?
Reading: offline. 测试测试 last answered 34 days 5 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 25 September 2026.
Map and rules
What rules does 测试测试 enforce, and what are its settings?
Reading the name gives no gather rate for 测试测试. The group cap is 8 players, which is the default in the game. survival, standard play of gathering, building and raiding — that is the game mode. Combat and raiding against other players are on. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.
Which map is live on 测试测试?
Check: map. Procedural, generated by the game, on 测试测试.
Join
What do you do to join 测试测试?
To join: start Rust, press F1 and type client.connect 39.144.114.143:20000. Or press Launch Rust here and Steam opens the game and connects you.