Rust Data

rustdata.spaceservers216.105.171.156:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 216.105.171.156:28015 checked 24d ago

Ray and Tina

Connect

srv = rust.server("216.105.171.156:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 2/30 # 7% full
7-day average 0 # peak –
rank #12,796 # top 57%
last wipe 25d ago # no schedule published
next wipe – # no rhythm it keeps

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, 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 Sep24 Sep28 Sep3 Oct7 Oct11 Oct

Top 57% 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 gap3.1 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak2players, last three wipes
crowd held75%else halves by day 3

The first 48 hours of its last wipes

Sun 4 OctFri 2 OctSun 27 Sep
00.511.52+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sun 4 Oct, 02:59 UTC25d ago 2 NaN running 2
1 Fri 2 Oct, 00:26 UTC27d ago 2 held half 2.1 days 0
2 Sun 27 Sep, 23:02 UTC31d ago 2 held half 4.1 days 0
3 Sun 20 Sep, 19:28 UTC38d ago 2 held half 7.1 days 0
4 Wed 16 Sep, 18:16 UTC43d ago 2 halved by day 3 4.1 days 2
5 Tue 15 Sep, 01:54 UTC44d ago 3 NaN 1.7 days 0
6 Mon 14 Sep, 00:17 UTC45d ago 3 NaN 1.1 days 1

# 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

2850 · seed 115612
Map of Ray and Tina
map
Procedural Map
size
2850
seed
115612
Open on RustMaps

Server

srv.info()
address
216.105.171.156:28015
region
–
max players
30
group limit
8, the default
wipe schedule
–
last wipe
4 Oct 2026, 02:59 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 · 512 on average321/375
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 317 on average440/475
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 280 on average970/1000
3Rustafied.com - EU FridayEU · groups of 16+ · weekly · 276 on average46/100
4eulongtest (private perf box)EU · groups of 14+ · monthly · 267 on average480/8
5Rustoria.co - EU MainEU · groups of 16+ · weekly · 265 on average979/1000

Quick answers

From the figures on this page.

Population

How does Ray and Tina compare in the rankings?

Rank #12,796 on seven-day player hours for Ray and Tina, within the top 57% of all ranked servers.

How full does Ray and Tina run?

The current row shows Ray and Tina offline; the last response was 24 days 18 hours ago.

Server data

Which Rust version is Ray and Tina on?

The build is Rust network protocol 2634 and build 166494 on Windows, run by Ray and Tina. The protocol has to match before you can join, and Steam does the updating.

How reliable is Ray and Tina, and is it up?

The latest sample has Ray and Tina offline, with a last sighting 24 days 18 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 13 September 2026.

Where does Ray and Tina sit?

There is no region published for Ray and Tina. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 216.105.171.156:28015.

Settings and map

What rules and settings are recorded for Ray and Tina?

The name Ray and Tina carries no gather rate. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. The server browser lists it under Community. Anti-cheat status: VAC on.

Which map has Ray and Tina loaded?

Ray and Tina runs a procedural map of size 2,850 with seed 115612, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.

Wipes and dates

When does Ray and Tina wipe, and how often?

Irregular wipe times on Ray and Tina leave no next wipe to forecast. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 25 days 16 hours ago, and that is the one in play.

On Ray and Tina, what happens on wipe day?

Recent wipes averaged 2 players at their peak. Peak population on the latest wipe came 0 hours in. Recent wipes kept the crowd above half the peak until the next wipe 75% of the time. Otherwise the crowd fell below half by day 3.

Tags and filters

Which Rust Data filters and lists contain Ray and Tina?

These Rust Data lists include Ray and Tina: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Which meanings do the tags on Ray and Tina hold?

These tags are published by Ray and Tina and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp30 (Max players): 30 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166494 (Build): The server runs build 166494; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not 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 into Ray and Tina?

In Rust, F1 opens the console: type client.connect 216.105.171.156:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp30,ptrak,$r?,v2634,gmrust,cs166494,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp30
Max players 30 slots in total.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs166494
Build The server runs build 166494.
ptrak
Networking The network layer is RakNet, standard for the game.
$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 103,740 players 11,898 servers online