Rust Data

rustdata.spaceservers204.111.39.122:27015.ipynb

Run all rust-data · live

‹ All servers

Online 204.111.39.122:28015 checked 9m ago

Tizen's Test Server

Connect

srv = rust.server("204.111.39.122:27015")
print(srv.connect_command)

Right now

srv.summary()
players now 0/1000 # 0% full
7-day average 0 # peak –
rank #15,290 # top 69%
last wipe 27d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
0123400:0009:0019:0003:0012:0021:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
02040608000:0009:0019:0003:0012:0021:00

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, measured since 17 Sep. 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
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 20 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 2 Oct, 00:04 UTC27d ago 1 NaN running 0

# 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

6000 · seed 1234
Map of Tizen's Test Server
map
Procedural Map
size
6000
seed
1234
Open on RustMaps

Server

srv.info()
address
204.111.39.122:28015
region
–
max players
1000
group limit
8, the default
wipe schedule
–
last wipe
2 Oct 2026, 00:04 UTC
hostname
–
first seen
13 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 499 on average140/250
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average173/250
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 283 on average535/675
3Rustafied.com - EU FridayEU · groups of 16+ · weekly · 277 on average29/100
4Rustoria.co - EU MainEU · groups of 16+ · weekly · 266 on average619/775
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 248 on average523/625

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does Tizen's Test Server rank?

Player hours over seven days put Tizen's Test Server at #15,290, in the top 69% of the ranked set.

How many players does Tizen's Test Server hold at once?

Tizen's Test Server reports 0 players at this refresh, with 1,000 slots configured. Over the last seven days it averaged 0 players.

Server facts

How smoothly does Tizen's Test Server run?

Server fps over the last 48 hours averages 56; the floor is 37. The entity count peaked at 203,739, covering buildings, deployables and the rest of the world. A high of 4,884 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

What Rust version does Tizen's Test Server run?

Version Rust network protocol 2635 and build 168909 on Windows is reported by Tizen's Test Server. Steam updates your game for you, but the protocol must match to join.

Is Tizen's Test Server up, and what does its uptime show?

Tizen's Test Server reports itself online at the current refresh. A restart about 6 days 23 hours ago is what its reported uptime implies. 167 of 168 hours up over the last 7 full days, or 99%. Its earliest recorded date in Rust Data is 13 September 2026.

In which location is Tizen's Test Server hosted?

There is no region published for Tizen's Test Server. 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 204.111.39.122:28015.

Settings and map

Which settings and rules does Tizen's Test Server run?

No gather rate appears in the name: Tizen's Test Server. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. The server browser lists it under Community. VAC is running: Valve's anti-cheat is on.

Which map has Tizen's Test Server loaded?

The game generates the map on Tizen's Test Server: procedural, size 6,000, seed 1234. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipes and dates

When does Tizen's Test Server wipe, and on what schedule?

The record for Tizen's Test Server holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 27 days 23 hours ago, and that is the one in play.

On Tizen's Test Server, what happens on wipe day?

The average peak over recent wipes is 1 players. Peak population on the latest wipe came 20 hours in.

Tags and filters

Which lists on Rust Data hold Tizen's Test Server, and which filters?

The Rust Data lists that Tizen's Test Server fits are: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Which meanings do the tags on Tizen's Test Server hold?

Read by the game's server browser, the tags Tizen's Test Server publishes are: gmrust (Game mode): Rust survival in its standard form; mp1000 (Max players): The server lists 1,000 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; sc1 (Custom tag): A plugin or the owner added this; standard Rust does not define it. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Join steps

What is the way into Tizen's Test Server?

The manual route: launch Rust, F1, then client.connect 204.111.39.122:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

Published as mp1000,ptrak,$r?,v2635,gmrust,cs168909,sc1,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp1000
Max players The server lists 1,000 slots.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Build number: 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code No region code is set.

Other

sc1
Custom tag A plugin or the owner added this; standard Rust does not define it.

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.

Rust Data 71,129 players 11,757 servers online