RUST METRICSFlight deck · live data
Data live Servers11,824 Players75,694 Populated3,728 Fresh wipes 3 h230 Scan5 min
‹ All servers85.72.240.52:35005
Offline Full Queue Fresh wipe Wipe due No query

Tin & Blood

Offline 85.72.240.52:35005 checked 38d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 0 /100

Players now

0% 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#15,491top 69%
Last wipe47d agono schedule published
Next wipe–no wipe seen yet
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 19 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 Sep22 Sep24 Sep26 Sep28 Sep30 Sep

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

PLAN

Wipe schedule

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
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.

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 timing

When does Tin & Blood wipe?

The rhythm of Tin & Blood's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 47 days 17 hours ago.

Tag meanings

Which tags does Tin & Blood carry, and what do they mean?

These are the tags Tin & Blood publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): Slots: 100; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs164530 (Build): Build 164530; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show Tin & Blood?

On Rust Metrics, Tin & Blood 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.

Occupancy

Where does Tin & Blood sit in the rankings?

Player hours over seven days put Tin & Blood at #15,491, in the top 69% of all ranked servers.

How full does Tin & Blood get?

Reading for Tin & Blood: offline at this moment; last seen 38 days 22 hours ago.

Operator and location

Where does Tin & Blood sit?

No region comes from Tin & Blood. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 85.72.240.52:35005.

What Rust version is Tin & Blood on?

Version check: Rust network protocol 2633 and build 164530 on Linux, run by Tin & Blood. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on Tin & Blood, and is it online?

Check: connection. Tin & Blood is offline at this moment. Last contact was 38 days 22 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 19 September 2026, recorded by Rust Metrics.

Rules and settings

What rules does Tin & Blood enforce, and what are its settings?

No gather rate appears in the name: Tin & Blood. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.

What map is Tin & Blood on?

From seed 1789661113, the game generates the procedural map on Tin & Blood. Its size is 6,000. The map repeats when size and seed match. Open it on RustMaps from this page.

Connection

How can you get onto Tin & Blood?

Press F1 in Rust and enter client.connect 85.72.240.52:35005. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2633,gmrust,cs164530,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players Slots: 100.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Your game must run protocol 2633 to get in.
cs164530
Build Build 164530.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.