测试
Offline 156.239.245.130:50000 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 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- 220/250
- 2/550
- 47/200
- 102/150
- 2/200
- 47/150
Quick answers
from the figures on this pageWipe timing
How often does 测试 wipe, and when?
Its rhythm cannot be told from the wipes of 测试 on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 18 days 6 hours ago.
Tag meanings
How should you read the tags on 测试?
Check: tags. The game's server browser reads gmvanilla (Game mode): Survival on vanilla settings; mp2 (Max players): Slots: 2; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167398 (Build): The server runs game build 167398; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is 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. These filters bring it up on the server list: Region: Asia; Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Population
Where does 测试 sit in the rankings?
Ranking for 测试: #15,769 on seven-day player hours, top 71% of all ranked servers.
What is the population on 测试?
Reading for 测试: offline at this moment; last seen 18 days 4 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 156.239.245.130:50000.
What Rust version is 测试 on?
Rust network protocol 2634 and build 167398 on Windows is the build 测试 runs. To get in, your game needs the same protocol; Steam applies the update.
How reliable is 测试, and is it online now?
Check: connection. 测试 is offline at this moment. Last contact was 18 days 4 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.
Map and rules
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. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. VAC is off. That is Valve's anti-cheat.
Which map is live on 测试?
The game generates a procedural map for 测试.
Connection
How do you connect to 测试?
To join: start Rust, press F1 and type client.connect 156.239.245.130:50000. Or press Launch Rust here and Steam opens the game and connects you.