Offline EA 183.221.149.37:33861 checked 39d ago
测试
Connect
srv = rust.server("183.221.149.37:24697")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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
Wipe schedule
srv.wipe_schedule()
Next wipe Thursday 29 October, 21:31 UTC, in 1d 21h. # Biweekly: 14 days after its last wipe
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())
Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 183.221.149.37:33861
- region
- EA
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- biweekly
- last wipe
- 17 Sep 2026, 21:31 UTC
- hostname
- –
- first seen
- 18 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | Rustoria.co - SEA Medium | EA · groups of 16+ · biweekly · 81 on average | 15/200 |
| 1 | Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com | EA · groups of 8+ · biweekly · 49 on average | 11/215 |
| 2 | Rustafied.com - SEA Medium | EA · groups of 16+ · biweekly · 32 on average | 10/100 |
| 3 | [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla | EA · groups of 8+ · biweekly · 5 on average | 0/200 |
| 4 | JP ONLY 2WEEK SOLO/DUO/TORIO#84 | EA · groups of 8+ · biweekly · 3 on average | 2/60 |
| 5 | [SEA] BRUNEI/MALAYSIA/INDONESIA | Rust Battleground | Biweekly | EA · groups of 8+ · biweekly · 2 on average | 1/100 |
Quick answers
From the figures on this page.
Player counts
How does 测试 compare in the rankings?
Ranked #15,392 on seven-day player hours, 测试 is #477 in Asia and in the top – of all ranked servers.
How full does 测试 run?
测试 returns no live count at this refresh, having last been seen 39 days 8 hours ago.
Server facts
Which Rust version is 测试 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.
Is 测试 up, and what does its uptime show?
测试 is offline at this refresh; the last response came 39 days 8 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 18 September 2026.
Where does 测试 sit?
The EA tag is what 测试 uses to list itself in Asia. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 183.221.149.37:33861.
Settings and map
Which rules apply on 测试, and what settings?
No gather rate appears in the name: 测试. The group limit sits at the default of 8 players. survival is the game mode here, and the usual game, with gathering, building and raiding. Raids and player combat are enabled. It is a community server, and the browser files it under Community. Vanilla, by its own description: facepunch's stock game, with rates, kits and rules untouched. Anti-cheat status: VAC on.
Which map has 测试 loaded?
A procedural map runs on 测试, generated by the game.
Wipes and dates
When does 测试 wipe, and on what schedule?
Expect an estimate: 测试's next wipe is projected from biweekly: 14 days after its last wipe. On Thursday 29 October at 21:31 UTC the next wipe is due. A new world was started 40 days 2 hours ago, and that is the one in play. Its tags carry a wipe schedule of every two weeks.
Tags, lists
Which lists on Rust Data hold 测试, and which filters?
The Rust Data lists that 测试 fits are: Rust community servers, unfiltered and Vanilla Rust servers. 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.
Which meanings do the tags on 测试 hold?
These tags are published by 测试 and read by the game's server browser: gmvanilla (Game mode): Survival in vanilla form; mp2 (Max players): 2 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs164530 (Build): Recorded game build: 164530; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^b (Biweekly): Two weeks between wipes; ^v (Vanilla): Facepunch's stock game, with rates, kits and rules untouched; EA (East Asia): East Asia is its listing in the server browser. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
How can I connect to 测试?
In Rust, F1 opens the console: type client.connect 183.221.149.37:33861. Launch Rust on this page does the same by opening the game through Steam and connecting.