RUST METRICSFlight deck · live data
Data live Servers11,866 Players94,541 Populated3,878 Fresh wipes 3 h396 Scan5 min
‹ All servers94.64.109.29:35005
Offline Full Queue Fresh wipe Wipe due No query

Tin & Blood

Offline 94.64.109.29:35005 checked 35d 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,643top 71%
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 23 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
15k10k15k20k23 Sep25 Sep26 Sep28 Sep29 Sep1 Oct

Top 71% 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

What wipe timing does Tin & Blood follow?

Its rhythm cannot be told from the wipes of Tin & Blood on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 47 days 19 hours ago the current world was made.

Lists and filters

How should you read the tags on Tin & Blood?

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): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): The server runs game build 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does Tin & Blood appear in Rust Metrics lists and filters?

These Rust Metrics lists carry Tin & Blood: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

What position does Tin & Blood hold among Rust servers?

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

How full does Tin & Blood get?

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

Operator and location

Which location does Tin & Blood run from?

No region tag on Tin & Blood. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 94.64.109.29:35005.

What Rust version is Tin & Blood on?

Rust network protocol 2633 and build 165217 on Linux is the build Tin & Blood runs. Matching protocol is required to join. Let Steam update your game.

Is Tin & Blood up, and how often does it stay up?

Check: connection. Tin & Blood is offline at this moment. Last contact was 35 days 6 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 23 September 2026.

Settings and map

What settings and rules apply on Tin & Blood?

Reading the name gives no gather rate for Tin & Blood. No limit is set beyond the default. Groups take up to 8 players. 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.

What map is Tin & Blood on?

Check: map. Procedural, size 6,000, seed 1789661113, generated by the game on Tin & Blood. The map repeats when size and seed match. Open it on RustMaps from this page.

Join

How can you get onto Tin & Blood?

To join: start Rust, press F1 and type client.connect 94.64.109.29:35005. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players Slots: 100.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Match the game version: protocol 2633 is required.
cs165217
Build The server runs game build 165217.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

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.