Station NA-16699 · no signal
TMR Staging
Offline NA 72.219.45.187:10002 checked 28d ago
- Players now
- 0/ 10
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #16,699
- top 70% · #1678 in NA
- Last wipe
- 28d ago
- monthly schedule
- Next wipe
- 7d 13h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 10 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 70% of all ranked servers, top 84% in NA. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 7d 13h. The force wipe · high confidence
- usual gap
- 9.4 daysbetween real wipes
- wipe-day peak
- 0players, last three wipes
Coming wipes
- 7d 13hThu 5 Nov, 19:00 UTCFW
- 35d 13hThu 3 Dec, 19:00 UTCFW
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| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Wed 30 Sep, 22:18 UTC28d ago | M0.0■steady | 0 | – | – | running | 0 |
| Mon 21 Sep, 13:38 UTC37d ago | M0.0■steady | 0 | – | – | 9.4 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer rules
Which map is running on TMR Staging?
TMR Staging uses a procedural map, which the game generates.
Which settings and rules apply on TMR Staging?
The name of TMR Staging gives no gather rate. At the game's default, groups can have up to 8 players. In pve mode, no player-versus-player fighting. The server browser lists it under Community, as a community server. The server has VAC on, Valve's anti-cheat.
Player counts
How many players are recorded on TMR Staging right now?
A reading taken now finds TMR Staging offline; the most recent activity was 28 days 6 hours ago.
How does TMR Staging rank against other Rust servers?
TMR Staging is #1,678 in North America and #16,699 worldwide on the past week's player hours, within the top 70% of ranked servers.
Server details
How reliably does TMR Staging stay online?
As recorded now, TMR Staging is not reachable, the last contact having been 28 days 6 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. Its earliest appearance in the records of Rust Server Trends dates to 19 September 2026.
Which region does TMR Staging run from?
With its NA tag, TMR Staging lists itself in North America. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 72.219.45.187:10002 is the address it uses.
What build of Rust does TMR Staging use?
TMR Staging is running Rust network protocol 2634 and build 166427 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
What does wipe day look like on TMR Staging?
The recent wipes averaged a busiest count of 0 players. 0 hours after the latest wipe, the crowd peaked.
On what timetable does TMR Staging run its wipes?
The force wipe is the only wipe TMR Staging takes, once a month. When every Rust server wipes, at the force wipe on Thursday 5 November at 19:00 UTC, it takes its next wipe. It has run its current world for 28 days 6 hours. Its tags state a monthly wipe schedule.
Server tags
What do the server tags on TMR Staging mean?
Tags published by TMR Staging and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp10 (Max players): Slots: 10; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs166427 (Build): The game build is 166427; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^m (Monthly): Wipes happen monthly, at the same time as Facepunch's force wipe; ^p (PvE): The danger comes from the world, not from other players; NA (North America): In the server browser it appears under North America. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does TMR Staging appear?
You will find TMR Staging on the following Rust Server Trends lists: Rust community servers without the side modes, Rust PvE servers and North America Rust servers. On the server list, the filters it matches are: 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.
Join the server
What steps get you onto TMR Staging?
Enter client.connect 72.219.45.187:10002 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.