Rust Server TrendsSeismic network · station log
Recording Stations11,700 Players41,781 Active3,029 Wipes · 3 h99 48 h

Station EA-15382 · no signal

测试

Offline EA 183.221.149.37:17292 checked 40d ago

biweekly wipes vanilla
Connect
Players now
0/ 2
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,382
#477 in EA
Last wipe
41d ago
biweekly schedule
Next wipe
19h
Thu 29 Oct, 21:31 UTC
Seismic record · station EA-15382 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 2 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep21 Sep22 Sep23 Sep24 Sep25 Sep
Expected events

Wipe schedule

Next wipe Thursday 29 October, 21:31 UTC, in 19h. Biweekly: 14 days after its last wipe

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Rustoria.co - SEA Medium EA · groups of 16+ · biweekly · 66 on average
5/ 200
Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com EA · groups of 8+ · biweekly · 41 on average
15/ 215
Rustafied.com - SEA Medium EA · groups of 16+ · biweekly · 27 on average
5/ 100
[SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla EA · groups of 8+ · biweekly · 4 on average
0/ 200
JP ONLY 2WEEK SOLO/DUO/TORIO#84 EA · groups of 8+ · biweekly · 3 on average
1/ 60
[SEA] BRUNEI/MALAYSIA/INDONESIA | Rust Battleground | Biweekly EA · groups of 8+ · biweekly · 2 on average
1/ 100
Readings, in words

Quick answers

from the figures on this page

Map and rules

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. At the game's default, groups can have up to 8 players. In survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. By its own description it is vanilla: rates, kits and rules are as Facepunch ships them. Anti-cheat is on: VAC, from Valve.

Live population

What is the current population on 测试?

A reading taken now finds 测试 offline; the most recent activity was 40 days 11 hours ago.

How does 测试 rank against other Rust servers?

For player hours across the last seven days, 测试 takes #15,382 overall and #477 in Asia, inside the top – of all ranked servers.

Operator and location

How reliably does 测试 stay online?

No contact with 测试 right now, and the last recorded contact was 40 days 11 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. Its earliest appearance in the records of Rust Server Trends dates to 18 September 2026.

Which region does 测试 run from?

With its EA tag, 测试 lists itself in Asia. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 183.221.149.37:17292 is the address it uses.

Which Rust version is 测试 running?

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 schedule

How often does 测试 wipe, and on which days?

An estimate from biweekly: 14 days after its last wipe gives 测试's next wipe. The date of its next wipe is Thursday 29 October at 21:31 UTC. 41 days 4 hours is how long the current world has been running. Its tags state that it wipes every two weeks.

Lists and tags

What do the server tags on 测试 mean?

Tags published by 测试 and read by the game's server browser include gmvanilla (Game mode): You'll find vanilla survival here; mp2 (Max players): 2 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs164530 (Build): The game build is 164530; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^b (Biweekly): The wipe cycle is two weeks; ^v (Vanilla): Rates, kits and rules are as Facepunch ships them; EA (East Asia): The server browser files it under East Asia. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does 测试 appear?

The Rust Server Trends lists that take in 测试 are: Rust community servers without the side modes and Vanilla Rust servers, recorded live. These filters bring it up on the server list: Region: Asia; Type: Vanilla, Community (not modded, not official) and No plugins at all; Server tag: Biweekly ^b and Vanilla ^v; Group limit: 5 or more; Wipe schedule: Every two weeks.

How to join

What steps get you onto 测试?

You can connect by pressing F1 in Rust and typing client.connect 183.221.149.37:17292 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp2,ptrak,$r?,v2633,^b,^v,EA,gmvanilla,cs164530,ts8

Game

gmvanilla
Game mode You'll find vanilla survival here.
mp2
Max players 2 slots are available.
ts8
Group limit This uses the game default of 8 per team.
v2633
Protocol To connect, your game must be on the same protocol, 2633.
cs164530
Build The game build is 164530.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code A region code has not been set.

Wipe schedule

^b
Biweekly The wipe cycle is two weeks.

Difficulty

^v
Vanilla Rates, kits and rules are as Facepunch ships them.

Region

EA
East Asia The server browser files it under East Asia.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

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.