Rust Server TrendsSeismic network · station log
Recording Stations11,909 Players102,314 Active3,972 Wipes · 3 h409 48 h

Station XX-16960 · no signal

测试1

Offline 125.118.193.126:40000 checked 31d ago

Connect
Players now
0/ 1
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#16,960
top 71%
Last wipe
31d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-16960 · 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 1 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
15k10k15k20k28 Sep29 Sep1 Oct2 Oct4 Oct5 Oct

Top 71% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force 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 Main EA · groups of 16+ · weekly · 181 on average
370/ 400
Japan Tokyo - Main|10/23|JP/KR/SEA|金曜日|JumpRust.com EA · groups of 16+ · weekly · 119 on average
16/ 550
Rustoria.co - SEA Long EA · groups of 12+ · monthly · 102 on average
55/ 200
Rustafied.com - SEA Main EA · groups of 16+ · weekly · 81 on average
167/ 450
Japan Beginner Server - BPwipe 10/23 [JP/KR/SEA|初心者] EA · groups of 8+ · weekly · 53 on average
10/ 200
[ASIA] Siam Rust | Vanilla | Weekly EA · groups of 8+ · weekly · 39 on average
106/ 180
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on 测试1?

测试1 uses a procedural map, which the game generates.

Which settings and rules apply on 测试1?

The name of 测试1 gives no gather rate. Groups hold up to 8 players, which is the default for the game. In survival mode, the usual game of gathering, building and raiding. You can raid and fight other players here. The server browser lists it under Community, as a community server. The server has VAC on, Valve's anti-cheat.

Player counts

How many players are recorded on 测试1 right now?

测试1 is not responding at this moment and is offline, last seen 31 days 3 hours ago.

How does 测试1 rank against other Rust servers?

The last seven days of player hours place 测试1 at #16,960, in the top 71% of all ranked servers.

Operator and location

How reliably does 测试1 stay online?

测试1 is down at the moment; the last recorded contact was 31 days 3 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. 28 September 2026 is when Rust Server Trends first recorded it.

Which region does 测试1 run from?

No region tag comes from 测试1, though the name points to Asia. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 125.118.193.126:40000.

Which Rust version is 测试1 running?

Rust network protocol 2633 and build 165217 on Windows is what 测试1 runs. The protocol must match for you to join, and Steam takes care of updating it.

Wipe day

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

On record so far are too few of 测试1's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 31 days 4 hours.

Tags

What do the server tags on 测试1 mean?

These are the tags 测试1 publishes for the browser to read: gmvanilla (Game mode): You'll find vanilla survival here; mp1 (Max players): Slots: 1; ts8 (Group limit): Teams max out at 8, the default set by the game; v2633 (Protocol): Game protocol 2633: to join, your game must match this version; cs165217 (Build): The game build is 165217; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code. 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 测试1 appear?

These Rust Server Trends lists include 测试1: Rust community servers without the side modes. You will find it under these filters on the server list: Region: Asia; Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

How to join

How do you connect to 测试1?

You can connect by pressing F1 in Rust and typing client.connect 125.118.193.126:40000 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 mp1,ptrak,$r?,v2633,gmvanilla,cs165217,ts8

Game

gmvanilla
Game mode You'll find vanilla survival here.
mp1
Max players Slots: 1.
ts8
Group limit Teams max out at 8, the default set by the game.
v2633
Protocol Game protocol 2633: to join, your game must match this version.
cs165217
Build The game build is 165217.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The server has no region code.

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.