Offline EA 103.152.113.67:28015 checked 19d ago
test01
Connect
srv = rust.server("103.152.113.67:28016")
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 bestTop 67% of all ranked servers, top 92% in EA. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Next wipe Friday 30 October, 05:49 UTC, in 1d 5h. # 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
- 103.152.113.67:28015
- region
- EA
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- biweekly
- last wipe
- 2 Oct 2026, 05:49 UTC
- hostname
- –
- first seen
- 9 Oct 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 · 66 on average | 5/200 |
| 1 | Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com | EA · groups of 8+ · biweekly · 42 on average | 15/215 |
| 2 | Rustafied.com - SEA Medium | EA · groups of 16+ · biweekly · 27 on average | 4/100 |
| 3 | [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla | EA · groups of 8+ · biweekly · 4 on average | 0/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.
Population
Against other Rust servers, how does test01 rank?
Player hours over the last seven days: #14,835 for test01, #482 in Asia, within the top 67% of the ranked set.
How many players does test01 hold at once?
The current row shows test01 offline; the last response was 19 days 13 hours ago.
About the server
What Rust version does test01 run?
The build is Rust network protocol 2634 and build 167398 on Windows, run by test01. Joining needs the same protocol on your game; Steam handles the update.
How reliable is test01, and is it up?
Offline now for test01, last seen 19 days 13 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 9 October 2026.
Where does test01 sit?
The EA tag is what test01 uses to list itself in Asia. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 103.152.113.67:28015 is its address.
Rules, settings, map
What rules and settings are recorded for test01?
No gather rate appears in the name: test01. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Combat and raiding between players: both allowed. The server browser lists it under Community. Anti-cheat status: VAC off.
Which map has test01 loaded?
A procedural map runs on test01, generated by the game.
Wipe data
When does test01 wipe, and how often?
Expect an estimate: test01's next wipe is projected from biweekly: 14 days after its last wipe. On Friday 30 October at 05:49 UTC the next wipe is due. A new world was started 26 days 18 hours ago, and that is the one in play. The tags list a two-weekly wipe cycle.
Tags and filters
Which lists on Rust Data hold test01, and which filters?
On Rust Data, test01 appears in these lists: Rust community servers, unfiltered. These filters bring it up on the server list: Region: Asia; Type: Community (not modded, not official) and No plugins at all; Server tag: Biweekly ^b; Group limit: 5 or more; Wipe schedule: Every two weeks.
Which meanings do the tags on test01 hold?
The game's server browser reads these tags from test01: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): Slot count: 1; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167398 (Build): The server runs build 167398; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^b (Biweekly): Two weeks between wipes; EA (East Asia): East Asia is its listing in the server browser. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way into test01?
In Rust, F1 opens the console: type client.connect 103.152.113.67:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.