Rust Data

rustdata.spaceservers183.221.149.16:24697.ipynb

Run all rust-data · live

‹ All servers

Offline 183.221.149.16:26690 checked 36d ago

测试

biweekly wipes vanillamoddedoxide

Connect

srv = rust.server("183.221.149.16:24697")
print(srv.connect_command)

Right now

srv.summary()
players now 0/2 # 0% full
7-day average 0 # peak –
rank #15,477 # top 68%
last wipe 36d ago # biweekly schedule
next wipe 5d 0h # Mon 2 Nov, 04:17 UTC

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k21 Sep22 Sep24 Sep25 Sep27 Sep28 Sep

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

Wipe schedule · from its schedule tag

srv.wipe_schedule()

Next wipe Monday 2 November, 04:17 UTC, in 5d 0h. # Its biweekly schedule tag · low confidence

wipe-day peak0players, last three wipes

Coming wipes

inatkind
05d 0hMon 2 Nov, 04:17 UTCwipe
18d 15hThu 5 Nov, 19:00 UTCFW force wipe
219d 0hMon 16 Nov, 04:17 UTCwipe
333d 0hMon 30 Nov, 04:17 UTCwipe
436d 15hThu 3 Dec, 19:00 UTCFW force wipe

The first 48 hours of its last wipes

No hourly players around its wipes yet.

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Mon 21 Sep, 04:17 UTC36d ago 0 NaN running 0

# 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.

display(srv.map, srv.info())

Map

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
183.221.149.16:26690
region
–
max players
2
group limit
8, the default
wipe schedule
biweekly
last wipe
21 Sep 2026, 04:17 UTC
hostname
–
first seen
21 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0[JP]初心者PVPサーバー|RaidTime・ EventsEA · groups of 10+ · biweekly · 19 on average7/100
1[JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29EA · no group limit · biweekly · 5 on average1/20
2瞌睡熊『5倍10废|10.28|萌新首选|无权限』EA · groups of 8+ · biweekly · 4 on average4/100
3[JP/PvE][BPリサーチ]MatoyServer初しん者〇EA · groups of 8+ · biweekly · 2 on average1/50
4[JPN] Apple Server | PvP | Vanilla | 2WeeklyEA · groups of 8+ · biweekly · 2 on average3/50
5cczsbwd/solo/独狼/原倍半月清/月图/公益服EA · no group limit · biweekly · 1 on average4/50

Quick answers

From the figures on this page.

Player counts

What position does 测试 take in the server rankings?

Over the last seven days 测试 sits at #15,477 on player hours, in the top 68% of ranked servers.

How full does 测试 run?

测试 returns no live count at this refresh, having last been seen 36 days 23 hours ago.

Server facts

What is the Rust version on 测试?

Rust network protocol 2633 and build 164530 on Windows is what 测试 runs. The protocol has to match before you can join, and Steam does the updating.

How reliable is 测试, and is it up?

The latest sample has 测试 offline, with a last sighting 36 days 23 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 21 September 2026.

Which location does 测试 run from?

Its name points to Asia, but 测试 publishes no region tag. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 183.221.149.16:26690.

Settings and map

Which rules apply on 测试, and what settings?

No gather rate appears in the name: 测试. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. Its own label is vanilla: untouched settings: rates, kits and rules as shipped. VAC is not running; Valve's anti-cheat is off.

Which map has 测试 selected?

The game generates its map: procedural, on 测试.

Wipe data

When does 测试 wipe, and on what schedule?

Too few wipes are on record for 测试 to confirm its schedule, so the tag drives the prediction. The schedule puts the next wipe on Monday 2 November at 04:17 UTC. The world it runs now was generated 36 days 23 hours ago. The tags list a two-weekly wipe cycle.

On 测试, what happens on wipe day?

Recent wipes averaged 0 players at their peak. The crowd on the latest wipe topped out 0 hours after it began.

Tags and filters

Which Rust Data filters and lists contain 测试?

On Rust Data, 测试 appears in these lists: Modded Rust servers. It appears under these filters 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.

Which meanings do the tags on 测试 hold?

Read by the game's server browser, the tags 测试 publishes are: gmvanilla (Game mode): Game mode: vanilla survival; mp2 (Max players): The server lists 2 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): To join, your game must run protocol 2633; cs164530 (Build): Recorded game build: 164530; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^b (Biweekly): Wipes run on a two-week cycle; ^v (Vanilla): Untouched settings: rates, kits and rules as shipped; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

How to join

How can I connect to 测试?

The manual route: launch Rust, F1, then client.connect 183.221.149.16:26690. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

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

Game

gmvanilla
Game mode Game mode: vanilla survival.
mp2
Max players The server lists 2 slots.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2633
Protocol To join, your game must run protocol 2633.
cs164530
Build Recorded game build: 164530.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code Region code: not set.

Wipe schedule

^b
Biweekly Wipes run on a two-week cycle.

Difficulty

^v
Vanilla Untouched settings: rates, kits and rules as shipped.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Modded listing: the game is changed by plugins or settings.

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.

Rust Data 35,785 players 11,617 servers online