Offline EA 103.152.113.57:28015 checked 25d ago
test01
Connect
srv = rust.server("103.152.113.57: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 60% of all ranked servers, top 88% 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 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
- 103.152.113.57: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
- 2 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 · 76 on average | 41/200 |
| 1 | Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com | EA · groups of 8+ · biweekly · 47 on average | 20/215 |
| 2 | Rustafied.com - SEA Medium | EA · groups of 16+ · biweekly · 31 on average | 13/100 |
| 3 | [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla | EA · groups of 8+ · biweekly · 5 on average | 1/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 | 0/100 |
Quick answers
From the figures on this page.
Player counts
What position does test01 take in the server rankings?
Player hours over the last seven days: #13,807 for test01, #466 in Asia, within the top 60% of the ranked set.
How many players does test01 hold at once?
test01 returns no live count at this refresh, having last been seen 25 days 15 hours ago.
Server data
What is the Rust version on test01?
Rust network protocol 2634 and build 166586 on Windows is what test01 runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is test01, and is it up?
test01 is offline at this refresh; the last response came 25 days 15 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 2 October 2026.
In which location is test01 hosted?
With its EA tag, test01 lists itself in Asia. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 103.152.113.57:28015.
Rules, settings, map
Which rules apply on test01, and what settings?
You will not find a gather rate in the string test01. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the usual game, with gathering, building and raiding. Raids and player combat are enabled. Community is its browser category. The VAC field reads off.
Which map has test01 selected?
test01 runs a procedural map, which the game generates.
Wipes and dates
On what schedule does test01 wipe?
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 2 hours ago, and that is the one in play. A fortnightly wipe schedule is published in its tags.
Lists and tags
Which lists on Rust Data hold test01, and which filters?
The Rust Data lists that test01 fits are: Rust community servers, unfiltered. Under these filters on the server list, it is listed: 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?
These tags are published by test01 and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp1 (Max players): 1 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166586 (Build): Build number: 166586; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^b (Biweekly): Two weeks between wipes; EA (East Asia): The server browser files it under East Asia. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
How can I connect to test01?
In Rust, F1 opens the console: type client.connect 103.152.113.57:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.