Station XX-15477 · no signal
测试
Offline 183.221.149.16:26690 checked 37d ago
- Players now
- 0/ 2
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,477
- top 68%
- Last wipe
- 37d ago
- biweekly schedule
- Next wipe
- 4d 9h
- Mon 2 Nov, 04:17 UTC
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 2 slots
- Motion · 24 h
- M –not enough readings
Players
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 68% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Monday 2 November, 04:17 UTC, in 4d 9h. Its biweekly schedule tag · low confidence
- wipe-day peak
- 0players, last three wipes
Coming wipes
- 4d 9hMon 2 Nov, 04:17 UTC
- 8d 0hThu 5 Nov, 19:00 UTCFW
- 18d 9hMon 16 Nov, 04:17 UTC
- 32d 9hMon 30 Nov, 04:17 UTC
- 36d 0hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Mon 21 Sep, 04:17 UTC37d ago | M0.0■steady | 0 | – | – | running | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageRules and settings
Which map is running on 测试?
A procedural map runs on 测试, generated by the game.
Which settings and rules apply on 测试?
The name of 测试 gives no gather rate. Groups hold up to 8 players, which is the default for the game. In survival mode, gather, build and raid in the standard game. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. Vanilla is the label it uses for itself: no changed rates, kits or rules: this is the game as Facepunch ships it. The server has VAC off, Valve's anti-cheat.
Live population
What is the current population on 测试?
测试 is not responding at this moment and is offline, last seen 37 days 14 hours ago.
How does 测试 rank against other Rust servers?
The last seven days of player hours place 测试 at #15,477, in the top 68% of all ranked servers.
Server facts
How reliably does 测试 stay online?
As recorded now, 测试 is not reachable, the last contact having been 37 days 14 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 21 September 2026.
Where in the world is 测试 hosted?
Its name points to Asia, but 测试 publishes no region tag. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 183.221.149.16:26690 is the address it uses.
What build of Rust does 测试 use?
On Windows, 测试 runs Rust network protocol 2633 and build 164530. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe pattern
What does wipe day look like on 测试?
On average, the busiest point of its recent wipes drew 0 players. 0 hours after the latest wipe, the crowd peaked.
On what timetable does 测试 run its wipes?
Its schedule cannot be confirmed, as too few of 测试's wipes are on record; the prediction follows its tag instead. Monday 2 November at 04:17 UTC is when its next wipe is due. 37 days 14 hours is how long the current world has been running. Every two weeks it wipes, according to the schedule in its tags.
Tags
What do the server tags on 测试 mean?
The game's server browser reads the tags 测试 publishes: gmvanilla (Game mode): Survival in vanilla mode; mp2 (Max players): The server has 2 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs164530 (Build): The game build is 164530; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server; ^b (Biweekly): The wipe cycle is two weeks; ^v (Vanilla): No changed rates, kits or rules: this is the game as Facepunch ships it; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does 测试 appear?
These Rust Server Trends lists include 测试: Modded Rust servers, tracked live. These filters bring it up on the server list: Region: Asia; Type: Vanilla and Modded; Server tag: Biweekly ^b, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.
How to join
How do you connect to 测试?
Enter client.connect 183.221.149.16:26690 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.