Offline EA 183.221.149.37:28015 checked 40d ago
测试
Connect
srv = rust.server("183.221.149.37:28017")
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 0h. # 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:28015
- region
- EA
- max players
- 40
- group limit
- 8, the default
- wipe schedule
- biweekly
- last wipe
- 17 Sep 2026, 21:31 UTC
- hostname
- –
- first seen
- 17 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 · 67 on average | 10/200 |
| 1 | Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com | EA · groups of 8+ · biweekly · 42 on average | 17/215 |
| 2 | Rustafied.com - SEA Medium | EA · groups of 16+ · biweekly · 27 on average | 11/100 |
| 3 | [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla | EA · groups of 8+ · biweekly · 4 on average | 1/200 |
| 4 | JP ONLY 2WEEK SOLO/DUO/TORIO#84 | EA · groups of 8+ · biweekly · 3 on average | 1/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?
Player hours over the last seven days: #15,392 for 测试, #477 in Asia, within the top – of the ranked set.
How full does 测试 run?
测试 returns no live count at this refresh, having last been seen 40 days 5 hours ago.
Server facts
What is the Rust version on 测试?
The build is Rust network protocol 2633 and build 164530 on Windows, run by 测试. Joining needs the same protocol on your game; Steam handles the update.
How reliable is 测试, and is it up?
测试 is offline at this refresh; the last response came 40 days 5 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 17 September 2026.
In which location is 测试 hosted?
In Asia, 测试 lists itself, using the EA 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.37:28015.
Settings and map
What rules and settings are recorded for 测试?
The name 测试 carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. Community is its browser category. The description says vanilla, which here means facepunch's stock game, with rates, kits and rules untouched. VAC, Valve's anti-cheat, is enabled.
Which map has 测试 selected?
A procedural map runs on 测试, generated by the game.
Wipe schedule
When does 测试 wipe, and how often?
An estimate from biweekly: 14 days after its last wipe gives 测试's next wipe. The schedule puts the next wipe on Thursday 29 October at 21:31 UTC. The world it runs now was generated 40 days 23 hours ago. A fortnightly wipe schedule is published in its tags.
Lists and tags
Where does 测试 appear among Rust Data lists and filters?
These Rust Data lists include 测试: 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; mp40 (Max players): Slot count: 40; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): To join, your game must run protocol 2633; cs164530 (Build): Recorded game build: 164530; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^b (Biweekly): Two weeks between wipes; ^v (Vanilla): Facepunch's stock game, with rates, kits and rules untouched; EA (East Asia): The server browser files it under East Asia. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way into 测试?
In Rust, F1 opens the console: type client.connect 183.221.149.37:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.