Rust Data

rustdata.spaceservers194.69.160.15:28033.ipynb

Run all rust-data · live

‹ All servers

Online 194.69.160.15:28031 checked 10m ago

Xeo

Connect

srv = rust.server("194.69.160.15:28033")
print(srv.connect_command)

Right now

srv.summary()
players now 0/?
7-day average 0 # peak –
rank #15,326 # top 69%
last wipe 7d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
0123414:0023:0008:0016:0002:0011:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
01020304014:0023:0008:0016:0002:0011: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 · no rhythm it keeps

srv.wipe_schedule()

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap1.1 daysbetween real wipes
on rhythm25%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Wed 21 OctThu 1 OctThu 24 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Wed 21 Oct, 18:05 UTC7d ago 0 NaN running 0
1 Thu 1 Oct, 11:23 UTC28d ago 1+1 queue halved by day 1 20.3 days 0
2 Thu 24 Sep, 15:06 UTC34d ago 1 halved by day 3 6.8 days 0
3 Wed 23 Sep, 23:38 UTC35d ago 1 NaN 0.6 days 0
4 Wed 23 Sep, 11:14 UTC36d ago 1 NaN 0.5 days 0
5 Thu 17 Sep, 11:38 UTC42d ago 1 halved by day 1 6 days 0
6 Wed 16 Sep, 13:21 UTC42d ago 1 NaN 0.9 days 0
7 Tue 15 Sep, 13:40 UTC43d ago 1 NaN 1 days 0
8 Mon 14 Sep, 07:05 UTC45d ago 1 NaN 1.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

4750 · seed 62131
Map of Xeo
map
Procedural Map
size
4750
seed
62131
Open on RustMaps

Server

srv.info()
address
194.69.160.15:28031
region
– · uk1
max players
–
group limit
8, the default
wipe schedule
–
last wipe
21 Oct 2026, 18:05 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 · 513 on average524/550
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average431/450
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average61/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 276 on average63/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 275 on average54/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 238 on average165/200

Quick answers

From the figures on this page.

Population data

What position does Xeo take in the server rankings?

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

What population does Xeo carry?

Point query at this second: Xeo returns 0 players. Over the last seven days it averaged 0 players.

About the server

How well does Xeo perform?

Server fps over the last 48 hours averages 21; the floor is 21. The entity count peaked at 131,000, covering buildings, deployables and the rest of the world. A high of 3,269 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.

What Rust version does Xeo run?

Version Rust network protocol 2635 and build 169205 on Linux is reported by Xeo. The protocol has to match before you can join, and Steam does the updating.

Is Xeo up, and what does its uptime show?

The current sample puts Xeo online. Count back 2 days 17 hours from its reported uptime to get the last restart. 167 of 168 hours up over the last 7 full days, or 99%. Rust Data logged it first on 13 September 2026.

In which location is Xeo hosted?

There is no region published for Xeo, and the region code is uk1. Rust Data does not look up where the machine stands; it shows where a server says it is. 194.69.160.15:28031 is its address.

Map and rules

Which rules apply on Xeo, and what settings?

You will not find a gather rate in the string Xeo. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. It is a community server, and the browser files it under Community. VAC is running: Valve's anti-cheat is on.

Which map has Xeo loaded?

Xeo runs a procedural map of size 4,750 with seed 62131, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.

Wipe data

On what schedule does Xeo wipe?

Irregular wipe times on Xeo leave no next wipe to forecast. 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 7 days 19 hours ago.

What is wipe day on Xeo like?

Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 0 hours after it began. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 1.

Tags, lists

Where does Xeo appear among Rust Data lists and filters?

The Rust Data lists that Xeo 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; Last wipe: In the last 2 weeks.

Which meanings do the tags on Xeo hold?

These tags are published by Xeo and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp0 (Max players): Slot count: 0; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs169205 (Build): The server runs build 169205; ptrak (Networking): The network layer is RakNet, standard for the game; $ruk1 (Region code): The row gives uk1 as its region code. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Join steps

How can I connect to Xeo?

The manual route: launch Rust, F1, then client.connect 194.69.160.15:28031. 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 mp0,ptrak,$ruk1,v2635,gmrust,cs169205,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp0
Max players Slot count: 0.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs169205
Build The server runs build 169205.
ptrak
Networking The network layer is RakNet, standard for the game.
$ruk1
Region code The row gives uk1 as its region code.

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 69,594 players 11,814 servers online