Offline EA 113.78.7.135:28015 checked 20d ago
test01
Connect
srv = rust.server("113.78.7.135: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 1d 7h. # 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
- 113.78.7.135: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
- 8 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 · 67 on average | 9/200 |
| 1 | Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com | EA · groups of 8+ · biweekly · 42 on average | 21/215 |
| 2 | Rustafied.com - SEA Medium | EA · groups of 16+ · biweekly · 27 on average | 9/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: #13,672 for test01, #469 in Asia, within the top 62% of the ranked set.
What population does test01 carry?
Offline now for test01, with the last sample 20 days 11 hours ago.
About the server
What is the Rust version on test01?
Rust network protocol 2634 and build 167231 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?
The latest sample has test01 offline, with a last sighting 20 days 11 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 8 October 2026.
Which location does test01 run from?
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. You can reach it at 113.78.7.135:28015.
Rules, settings, map
Which settings and rules does test01 run?
No gather rate appears in the name: 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. The server browser lists it under Community. VAC is not running; Valve's anti-cheat is 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?
An estimate from biweekly: 14 days after its last wipe gives test01's next wipe. The schedule puts the next wipe on Friday 30 October at 05:49 UTC. This world was created 26 days 16 hours ago. Its tags carry a wipe schedule of every two weeks.
Tags and filters
Which lists on Rust Data hold test01, and which filters?
These Rust Data lists include test01: 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?
The game's server browser reads these tags from test01: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): The server lists 1 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167231 (Build): The server runs build 167231; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^b (Biweekly): Wipes run on a two-week cycle; EA (East Asia): The server browser files it under East Asia. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
What is the way to join test01?
The manual route: launch Rust, F1, then client.connect 113.78.7.135:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.