Rust Data

rustdata.spaceservers178.70.11.224:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 178.70.11.224:28015 checked 23d ago

chibaka

Connect

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

Right now

srv.summary()
players now 1/3 # 33% full
7-day average 0 # peak –
rank #13,797 # top 61%
last wipe 23d ago # no schedule published
next wipe – # no wipe seen yet

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
15k10k15k20k5 Oct6 Oct8 Oct9 Oct11 Oct12 Oct

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

Wipe schedule

srv.wipe_schedule()

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_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

Custom map, no picture published
map
Custom Map
size
–
seed
–

Server

srv.info()
address
178.70.11.224:28015
region
–
max players
3
group limit
8, the default
wipe schedule
–
last wipe
5 Oct 2026, 12:45 UTC
hostname
–
first seen
5 Oct 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 · 560 on average169/250
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average108/200
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average16/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 288 on average15/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 274 on average16/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 250 on average21/200

Quick answers

From the figures on this page.

Population

What position does chibaka take in the server rankings?

Player hours over seven days put chibaka at #13,797, in the top 61% of the ranked set.

How many players does chibaka hold at once?

chibaka returns no live count at this refresh, having last been seen 23 days 13 hours ago.

Server data

Which Rust version is chibaka on?

The build is Rust network protocol 2634 and build 166652 on Windows, run by chibaka. Steam updates your game for you, but the protocol must match to join.

Is chibaka up, and what does its uptime show?

Offline now for chibaka, last seen 23 days 13 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 5 October 2026.

In which location is chibaka hosted?

For chibaka, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 178.70.11.224:28015 is its address.

Map and rules

Which settings and rules does chibaka run?

You will not find a gather rate in the string chibaka. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Raids and player combat are enabled. The server browser lists it under Community. Anti-cheat status: VAC on.

Wipes and dates

When does chibaka wipe, and how often?

Too few wipes are on record for chibaka to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 23 days 13 hours ago.

Lists and tags

Where does chibaka appear among Rust Data lists and filters?

These Rust Data lists include chibaka: 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.

How should you read the server tags on chibaka?

The game's server browser reads these tags from chibaka: gmrust (Game mode): Survival play, standard Rust; mp3 (Max players): 3 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166652 (Build): Build number: 166652; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Connecting

How can I connect to chibaka?

Enter client.connect 178.70.11.224: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 mp3,ptrak,$r?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp3
Max players 3 slots in total.
ts8
Group limit Team limit of 8, as shipped by default.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs166652
Build Build number: 166652.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code Region code: not 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 37,607 players 11,693 servers online