Rust Data

rustdata.spaceservers152.89.199.149:35010.ipynb

Run all rust-data · live

‹ All servers

Online 152.89.199.149:35000 checked 10m ago

Test Z

Connect

srv = rust.server("152.89.199.149:35010")
print(srv.connect_command)

Right now

srv.summary()
players now 0/100 # 0% full
7-day average 0 # peak 1
rank #15,251 # top 69%
last wipe 25d ago # no schedule published
next wipe – # too few wipes seen yet
display(Image(srv.banner))

Players

srv.players.plot(range="48h")
AveragePeak
0123408:0017:0002:0011:0020:0005:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020008:0017:0002:0011:0020:0005: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 Sep5 Oct13 Oct20 Oct28 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.

usual gap5.3 daysbetween real wipes
wipe-day peak54players, last three wipes

The first 48 hours of its last wipes

Wed 7 OctFri 2 Oct
020406080+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 107, 13 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Wed 7 Oct, 17:14 UTC20d ago 107 NaN running 0
1 Fri 2 Oct, 09:12 UTC25d ago 0 NaN 5.3 days 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

3500 · seed 5395053
No map picture published
map
Procedural Map
size
3500
seed
5395053
Open on RustMaps

Server

srv.info()
address
152.89.199.149:35000
region
–
max players
100
group limit
8, the default
wipe schedule
–
last wipe
2 Oct 2026, 09:12 UTC
hostname
main.x4c.ru
first seen
14 Sep 2026

Operator · x4c.ru

rust.servers(operator="x4c.ru").sort_values("players")
serverplayers

The only server publishing a x4c.ru hostname.

About this server · in its own words

print(srv.description)
Ванильный сервер без модификаций, идеально подходит для новичков Геймплей такой, как его задумали разработчики игры — Эффективный серверный античит и модерация нечестных игроков — Бесплатная рулетка на сайте каждые 4 часа — Включена поддержка приложения RUST+ — Администрация следит за сервером без вмешательства в игровой процесс — Переработчик в рыбацкой деревне, на сфере, карго и нефтяных вышках

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 · 535 on average325/300
1Rustoria.co - EU MainEU · groups of 16+ · weekly · 320 on average22/250
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 319 on average19/250
3Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average201/200
4Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 277 on average97/200
5Rustafied.com - EU FridayEU · groups of 16+ · weekly · 265 on average30/100

Quick answers

From the figures on this page.

Player counts

What position does Test Z take in the server rankings?

Rank #15,251 on seven-day player hours for Test Z, within the top 69% of all ranked servers.

What population does Test Z carry?

Current row: 0 players on Test Z, against 100 slots. Over the last seven days it averaged 0 players and peaked at 1.

Server facts

How well does Test Z perform?

Server fps over the last 48 hours averages 115; the floor is 93. The entity count peaked at 71,492, covering buildings, deployables and the rest of the world. A high of 2,606 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.

What Rust version does Test Z run?

The build is Rust network protocol 2635 and build 168909 on Linux, run by Test Z. Joining needs the same protocol on your game; Steam handles the update.

How reliable is Test Z, and is it online now?

Online is the state at the latest refresh for Test Z. The uptime it reports puts the last restart about 3 days 22 hours ago. Over the last 7 full days the hours up number 168 of 168, 100%. The first row Rust Data holds for it is dated 14 September 2026.

Which location does Test Z run from?

No region is published by Test Z. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 152.89.199.149:35000.

Rules, settings, map

What rules and settings are recorded for Test Z?

The name Test Z carries no gather rate. The group limit sits at the default of 8 players. survival is the game mode here, and 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. VAC, Valve's anti-cheat, is enabled.

Which map has Test Z selected?

Test Z runs a procedural map of size 3,500 with seed 5395053, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipes and dates

On what schedule does Test Z wipe?

Too few wipes are on record for Test Z to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 25 days 21 hours ago.

What is wipe day on Test Z like?

Across recent wipes the busiest point averaged 54 players. The crowd on the latest wipe topped out 13 hours after it began.

Tags and filters

Which Rust Data filters and lists contain Test Z?

These Rust Data lists include Test Z: Rust community servers, unfiltered. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Who is behind Test Z?

No other server we track uses the x4c.ru hostname that Test Z publishes.

How should you read the server tags on Test Z?

Read by the game's server browser, the tags Test Z publishes are: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): The server lists 100 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set. 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.

Connecting

What is the way to join Test Z?

Enter client.connect 152.89.199.149:35000 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. https://x4c.ru is the website recorded for it.

Server tags · what each one means

srv.tags.decode()

Published as mp100,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp100
Max players The server lists 100 slots.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Recorded game build: 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code No region code is set.

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 38,873 players 11,630 servers online