Working its way up from the back of the class: #15,491 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
27/ 100
F
Lost ground: down 7,267 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to F.
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeak
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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.
Rank
daily · 1 is best
RankRank in region
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
No region is published for Tin & Blood. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 85.72.240.52:35005.
How reliable is Tin & Blood, and is it up?
At this moment, Tin & Blood is offline; the last time it was seen was 37 days 12 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 19 September 2026.
On what Rust version does Tin & Blood sit?
Rust network protocol 2633 and build 164530 on Linux is what Tin & Blood runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
When does Tin & Blood wipe, and how often?
Tin & Blood has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 46 days 7 hours.
Player numbers
Where does Tin & Blood place in the wider field of Rust servers?
Over the last seven days, Tin & Blood has #15,491 for player hours, in the top 69% of all ranked servers.
How many players does Tin & Blood usually have?
The last sighting of Tin & Blood was 37 days 12 hours ago, and it is offline right now.
Lists and filters
What is meant by the tags on Tin & Blood?
gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): 100 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs164530 (Build): Build number: 164530; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set are the tags Tin & Blood publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does Tin & Blood appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Tin & Blood among them: Best community servers, graded. 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.
Rules and settings
What settings and rules apply on Tin & Blood?
You will find no gather rate in the name of Tin & Blood. With no change from the game default, groups take up to 8 players. It runs survival, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. You will see it in the Community section of the server browser, since it is a community server. The server runs Valve's anti-cheat, VAC.
Can you tell me which map Tin & Blood uses?
Tin & Blood runs a game-generated procedural map at size 6,000, seed 1789661113. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
How do you get onto Tin & Blood?
Enter client.connect 85.72.240.52:35005 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2633,gmrust,cs164530,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max players100 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs164530
BuildBuild number: 164530.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been 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.
A term to build on. Even marks across the subjects, from F to F.