测试测试
Offline 39.144.114.130: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- 132/200
- 0/550
- 31/200
- 42/100
- 1/200
- 22/150
Quick answers
from the figures on this pageWipe schedule
When does 测试测试 wipe?
To tell the rhythm of 测试测试, too few of its wipes 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 57 days 1 hours ago.
Tag meanings
How should you read the tags on 测试测试?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; 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): Build 162434; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty from 测试测试. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Which lists and filters on Rust Metrics show 测试测试?
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
What position does 测试测试 hold among Rust servers?
Ranking for 测试测试: #15,826 on seven-day player hours, top 72% of all ranked servers.
What player count does 测试测试 carry?
测试测试 is not responding; status offline, last seen 18 days 14 hours ago.
Server details
Which location does 测试测试 run from?
Check: location. No region tag comes from 测试测试, but the name points to Asia. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 39.144.114.130: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?
Check: connection. 测试测试 is offline at this moment. Last contact was 18 days 14 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 11 October 2026.
Settings and map
What settings and rules apply on 测试测试?
Check: gather rate. The name 测试测试 does not state one. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Community server. VAC is on. That is Valve's anti-cheat.
Which map is live on 测试测试?
The game generates a procedural map for 测试测试.
How to join
What do you do to join 测试测试?
Press F1 in Rust and enter client.connect 39.144.114.130:20000. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.