Offline EA 59.39.216.190:28015 checked 21d ago
test01
Connect
srv = rust.server("59.39.216.190: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 62% of all ranked servers, top 90% 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 9h. # 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
- 59.39.216.190: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
- 7 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 · 75 on average | 221/250 |
| 1 | Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com | EA · groups of 8+ · biweekly · 36 on average | 11/215 |
| 2 | Rustafied.com - SEA Medium | EA · groups of 16+ · biweekly · 29 on average | 80/100 |
| 3 | [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla | EA · groups of 8+ · biweekly · 4 on average | 18/200 |
| 4 | [SEA] BRUNEI/MALAYSIA/INDONESIA | Rust Battleground | Biweekly | EA · groups of 8+ · biweekly · 2 on average | 5/100 |
| 5 | 新手村 | Rookie Village | 四人 | 1x PVP 10.26新开 | EA · groups of 8+ · 1x · biweekly · 1 on average | 0/500 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does test01 rank?
On seven-day player hours test01 is #13,672 overall and #476 in Asia, inside the top 62% of all ranked servers.
What population does test01 carry?
test01 returns no live count at this refresh, having last been seen 21 days 22 hours ago.
About the server
What is the Rust version on test01?
Rust network protocol 2634 and build 167058 on Windows is what test01 runs. The protocol has to match before you can join, and Steam does the updating.
Is test01 up, and what does its uptime show?
Offline now for test01, last seen 21 days 22 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 7 October 2026.
Where does test01 sit?
In Asia, test01 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. 59.39.216.190:28015 is its address.
Settings and map
Which rules apply on test01, and what settings?
You will not find a gather rate in the string test01. The group limit sits at the default of 8 players. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. It is a community server, and the browser files it under Community. VAC is not running; Valve's anti-cheat is off.
Which map has test01 selected?
The game generates its map: procedural, on test01.
Wipes and dates
When does test01 wipe, and how often?
The next wipe for test01 is an estimate, drawn from biweekly: 14 days after its last wipe. The schedule puts the next wipe on Friday 30 October at 05:49 UTC. This world was created 27 days 14 hours ago. A fortnightly wipe schedule is published in its tags.
Tags and filters
Where does test01 appear among Rust Data lists and filters?
The Rust Data lists that test01 fits are: 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.
How should you read the server tags on test01?
Read by the game's server browser, the tags test01 publishes are: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): The server lists 1 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167058 (Build): The server runs build 167058; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^b (Biweekly): The cycle is fourteen days; 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 test01?
In Rust, F1 opens the console: type client.connect 59.39.216.190:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.