Offline EA 113.78.5.219:28015 checked 41d ago

test01

biweekly wipes

Connect

srv = rust.server("113.78.5.219:28016")
print(srv.connect_command)

Launch Rust and join

Right now

srv.summary()

players now 1/1 # 100% full

7-day average 0 # peak –

rank #13,247 # #461 in EA

last wipe 54d ago # biweekly schedule

next wipe 1d 8h # Fri 30 Oct, 05:02 UTC

Players

srv.players.plot(range="48h")

No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")

This server has not answered a direct query in the last 48 hours.

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

RankRank in region

Wipe schedule

srv.wipe_schedule()

Next wipe Friday 30 October, 05:02 UTC, in 1d 8h. # Biweekly: 14 days after its last wipe

Wipes · newest first

srv.wipes.head(20)

	wiped	peak	crowd	lasted	players_before
	datetime64[UTC]	int64	object	timedelta	int64
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

No map picture published

map: Procedural Map
size: –
seed: –

Server

srv.info()

<class 'rust.Server'>
Index: 8 entries, address to first_seen

address: 113.78.5.219:28015
region: EA
max players: 1
group limit: 8, the default
wipe schedule: biweekly
last wipe: 4 Sep 2026, 05:02 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 · 68 on average	11/200
1	Japan Tokyo - Mondays\|10/19\|JP/KR/SEA\|2週間\|JumpRust.com	EA · groups of 8+ · biweekly · 42 on average	19/215
2	Rustafied.com - SEA Medium	EA · groups of 16+ · biweekly · 27 on average	13/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	0/100

Quick answers

From the figures on this page.

Population data

What position does test01 take in the server rankings?

On seven-day player hours test01 is #13,247 overall and #461 in Asia, inside the top – of all ranked servers.

How many players does test01 hold at once?

test01 returns no live count at this refresh, having last been seen 41 days ago.

Server facts

What is the Rust version on test01?

Version Rust network protocol 2633 and build 164530 on Windows is reported by test01. 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 41 days ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 17 September 2026.

In which location is test01 hosted?

In Asia, test01 lists itself, using the EA tag. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 113.78.5.219:28015.

Map and rules

Which rules apply on test01, and what settings?

You will not find a gather rate in the string test01. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Combat and raiding between players: both allowed. It is a community server, and the browser files it under Community. The VAC field reads off.

Which map has test01 selected?

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. The schedule puts the next wipe on Friday 30 October at 05:02 UTC. The world it runs now was generated 54 days 15 hours ago. A fortnightly wipe schedule is published in its tags.

Tags, lists

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?

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): Unchanged from default, teams hold up to 8; v2633 (Protocol): To join, your game must run protocol 2633; cs164530 (Build): Recorded game build: 164530; 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): In the server browser it sits 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.

Join steps

What is the way into test01?

Enter client.connect 113.78.5.219:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

Published as mp1,ptrak,$r?,v2633,^b,EA,gmrust,cs164530,ts8

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.