Online 76.37.92.54:28015 checked 9m ago
Tinmans Server
Connect
srv = rust.server("76.37.92.54:28017")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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. 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 bestTop 23% 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.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 23 Oct, 11:05 UTC5d ago | 1 | NaN | running | 1 |
| 1 | Mon 12 Oct, 15:03 UTC15d ago | 1 | NaN | 10.8 days | 1 |
| 2 | Sun 11 Oct, 22:51 UTC16d ago | 1 | NaN | 0.7 days | 0 |
| 3 | Thu 24 Sep, 17:07 UTC33d ago | 1 | held half | 17.2 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 76.37.92.54:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 23 Oct 2026, 14:51 UTC
- hostname
- –
- first seen
- 17 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 543 on average | 673/725 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 318 on average | 433/475 |
| 2 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 308 on average | 40/250 |
| 3 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 308 on average | 54/250 |
| 4 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 268 on average | 230/250 |
| 5 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 266 on average | 127/175 |
Quick answers
From the figures on this page.
Player counts
How does Tinmans Server compare in the rankings?
Player hours over seven days put Tinmans Server at #5,143, in the top 23% of the ranked set.
What population does Tinmans Server carry?
The sample now reads 1 players for Tinmans Server, out of 50 slots. Over the last seven days it averaged 1 players and peaked at 1. The 48-hour sample puts the busiest hour at 14:00 UTC, averaging 1 players.
About the server
Which Rust version is Tinmans Server on?
Rust network protocol 2635 and build 168909 on Windows is what Tinmans Server runs. Steam updates your game for you, but the protocol must match to join.
How reliable is Tinmans Server, and is it online now?
Online is the state at the latest refresh for Tinmans Server. 55 of 168 hours up over the last 7 full days, or 33%. Its earliest recorded date in Rust Data is 17 September 2026.
Which location does Tinmans Server run from?
There is no region published for Tinmans Server. Rust Data does not look up where the machine stands; it shows where a server says it is. 76.37.92.54:28015 is its address.
Rules, settings, map
Which rules apply on Tinmans Server, and what settings?
No gather rate appears in the name: Tinmans Server. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. It is a community server, and the browser files it under Community. VAC is running: Valve's anti-cheat is on.
Which map has Tinmans Server selected?
A procedural map runs on Tinmans Server, generated by the game.
Wipes and dates
On what schedule does Tinmans Server wipe?
No next wipe can be predicted for Tinmans Server, which wipes at irregular times. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 4 days 22 hours ago, and that is the one in play.
On Tinmans Server, what happens on wipe day?
Recent wipes averaged 1 players at their peak. The crowd on the latest wipe topped out 0 hours after it began. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.
Tags and filters
Where does Tinmans Server appear among Rust Data lists and filters?
The Rust Data lists that Tinmans Server fits are: Rust community servers, unfiltered. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.
Which meanings do the tags on Tinmans Server hold?
These tags are published by Tinmans Server and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way to join Tinmans Server?
Enter client.connect 76.37.92.54:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.