Offline NA 72.219.45.187:10002 checked 28d ago
TMR Staging
Connect
srv = rust.server("72.219.45.187:10003")
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 70% of all ranked servers, top 84% in NA. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 8h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 8h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 8h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 30 Sep, 22:18 UTC28d ago | 0 | NaN | running | 0 |
| 1 | Mon 21 Sep, 13:38 UTC37d ago | 0 | NaN | 9.4 days | 0 |
# 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
- 72.219.45.187:10002
- region
- NA
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 30 Sep 2026, 22:18 UTC
- hostname
- –
- first seen
- 19 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 | ABYSS | PvE | US | Vanilla | Noob Friendly | NA · groups of 8+ · monthly · 54 on average | 13/200 |
| 1 | [US] RustEZ Pure PvE | Low Decay | No Killing | No Raiding | NA · groups of 8+ · monthly · 31 on average | 13/200 |
| 2 | Rusty Spoons PvE | no raiding / stealing / killing | NA · groups of 10+ · monthly · 13 on average | 1/100 |
| 3 | MadRust PVE - Get Achievements | NA · groups of 8+ · monthly · 12 on average | 8/50 |
| 4 | [US] PureRust | PvE | No Decay | No Killing | No Raiding | NA · groups of 8+ · monthly · 11 on average | 0/150 |
| 5 | Stillwater Shores PVE | PVP | NA · groups of 30+ · monthly · 6 on average | 2/100 |
Quick answers
From the figures on this page.
Population
How does TMR Staging compare in the rankings?
Ranked #16,699 on seven-day player hours, TMR Staging is #1,678 in North America and in the top 70% of all ranked servers.
How full does TMR Staging run?
The current row shows TMR Staging offline; the last response was 28 days 11 hours ago.
About the server
Which Rust version is TMR Staging on?
The build is Rust network protocol 2634 and build 166427 on Windows, run by TMR Staging. Joining needs the same protocol on your game; Steam handles the update.
Is TMR Staging up, and what does its uptime show?
The latest sample has TMR Staging offline, with a last sighting 28 days 11 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 19 September 2026.
Which location does TMR Staging run from?
The NA tag is what TMR Staging uses to list itself in North America. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 72.219.45.187:10002 is its address.
Map and rules
What rules and settings are recorded for TMR Staging?
You will not find a gather rate in the string TMR Staging. No custom cap; the default of 8 players per group stands. pve is the game mode here, and no combat between players. Community is its browser category. VAC, Valve's anti-cheat, is enabled.
Which map has TMR Staging loaded?
The game generates its map: procedural, on TMR Staging.
Wipes and dates
When does TMR Staging wipe, and how often?
Once a month TMR Staging wipes, with the force wipe. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. The world it runs now was generated 28 days 11 hours ago. The tags list wipes as monthly.
On TMR Staging, what happens on wipe day?
Recent wipes averaged 0 players at their peak. The crowd on the latest wipe topped out 0 hours after it began.
Tags and filters
Where does TMR Staging appear among Rust Data lists and filters?
These Rust Data lists include TMR Staging: Rust community servers, unfiltered, Rust PvE servers and North America Rust servers. Under these filters on the server list, it is listed: Region: North America; Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: Monthly ^m and PvE ^p; Group limit: 5 or more; Wipe schedule: Monthly.
Which meanings do the tags on TMR Staging hold?
These tags are published by TMR Staging and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): Slot count: 10; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs166427 (Build): Build number: 166427; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^m (Monthly): Monthly: the wipe lands with Facepunch's force wipe; ^p (PvE): No player-versus-player combat; the danger comes from the world; NA (North America): The server browser files it under North America. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way to join TMR Staging?
In Rust, F1 opens the console: type client.connect 72.219.45.187:10002. Launch Rust on this page does the same by opening the game through Steam and connecting.