RUST METRICSFlight deck · live data
Data live Servers11,722 Players62,389 Populated3,280 Fresh wipes 3 h180 Scan5 min
‹ All servers216.105.171.156:28015
Offline Full Queue Fresh wipe Wipe due No query

Ray and Tina

Offline 216.105.171.156:28015 checked 24d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 8 15 22 30 PAX 2 /30

Players now

7% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#12,796top 57%
Last wipe25d agono schedule published
Next wipe–no rhythm it keeps
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

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.

REC 3

Rank

daily · 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.

PLAN

Wipe schedule

no rhythm it keeps

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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 4 Oct, 02:59 UTC25d ago 2 – running 2
Fri 2 Oct, 00:26 UTC27d ago 2 held half 2.1 days 0
Sun 27 Sep, 23:02 UTC32d ago 2 held half 4.1 days 0
Sun 20 Sep, 19:28 UTC39d ago 2 held half 7.1 days 0
Wed 16 Sep, 18:16 UTC43d ago 2 halved by day 3 4.1 days 2
Tue 15 Sep, 01:54 UTC44d ago 3 – 1.7 days 0
Mon 14 Sep, 00:17 UTC46d ago 3 – 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

What should you expect from wipe day on Ray and Tina?

An average of 2 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 0 hours. Above half that peak the crowd stayed until the next wipe in 75% of recent wipes. It fell below half by day 3 when it didn't.

What wipe timing does Ray and Tina follow?

No next wipe can be predicted for Ray and Tina, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 25 days 21 hours ago the current world was made.

Tag meanings

How should you read the tags on Ray and Tina?

These are the tags Ray and Tina publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp30 (Max players): The server holds 30 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166494 (Build): Game build reading: 166494; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Ray and Tina appear in Rust Metrics lists and filters?

On Rust Metrics, Ray and Tina sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

What position does Ray and Tina hold among Rust servers?

Player hours over seven days put Ray and Tina at #12,796, in the top 57% of all ranked servers.

How full does Ray and Tina get?

Status for Ray and Tina: offline. Last seen 24 days 23 hours ago.

Server details

What location is Ray and Tina hosted in?

No region comes from Ray and Tina. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 216.105.171.156:28015.

What Rust version is Ray and Tina on?

Rust network protocol 2634 and build 166494 on Windows is the build Ray and Tina runs. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on Ray and Tina, and is it online?

Ray and Tina reports offline. The last reading came 24 days 23 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

What rules does Ray and Tina enforce, and what are its settings?

No gather rate appears in the name: Ray and Tina. The group cap is 8 players, which is the default in the game. survival, the normal game: build, gather, raid — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. VAC is on. That is Valve's anti-cheat.

Which map is live on Ray and Tina?

Size 2,850 and seed 115612: the game generates the procedural map on Ray and Tina from them. The map repeats when size and seed match. Open it on RustMaps from this page.

Join

How do you connect to Ray and Tina?

Check: join. Open Rust, press F1, then enter client.connect 216.105.171.156:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp30
Max players The server holds 30 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166494
Build Game build reading: 166494.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.