测试测试
Offline 39.144.114.139:20000 checked 21d 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- 200/200
- 2/550
- 38/200
- 69/100
- 1/200
- 47/150
Quick answers
from the figures on this pageWipe timing
What wipe timing does 测试测试 follow?
To tell the rhythm of 测试测试, too few of its wipes 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. 57 days 5 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): The game mode is plain Rust survival; mp40 (Max players): The server holds 40 slots; ts8 (Group limit): Default limit in force: 8 per team; v2632 (Protocol): Your game must run protocol 2632 to get in; cs162434 (Build): Build 162434; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty from 测试测试. 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 测试测试?
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.
Population
What position does 测试测试 hold among Rust servers?
Player hours over seven days put 测试测试 at #15,835, in the top 72% of all ranked servers.
What is the population on 测试测试?
测试测试 is not responding; status offline, last seen 21 days 8 hours ago.
Operator and location
Where does 测试测试 sit?
Check: location. No region tag comes from 测试测试, but the name points to Asia. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 39.144.114.139:20000.
What Rust version is 测试测试 on?
Reading: 测试测试, Rust network protocol 2632 and build 162434, Linux. Matching protocol is required to join. Let Steam update your game.
What is the uptime on 测试测试, and is it online?
测试测试 reports offline. The last reading came 21 days 8 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 25 September 2026.
Map and rules
What settings and rules apply on 测试测试?
Reading the name gives no gather rate for 测试测试. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.
What map is 测试测试 on?
Procedural map on 测试测试, made by the game's generator.
How to join
How do you connect to 测试测试?
To join: start Rust, press F1 and type client.connect 39.144.114.139:20000. Or press Launch Rust here and Steam opens the game and connects you.