Station AF-11239 · recording
TMR Testing
Online AF 102.211.186.108:10010 checked 11m ago
- Players now
- 0/ 60
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak 1
- Rank
- #11,239
- top 50% · #19 in AF
- Last wipe
- 27d ago
- monthly schedule
- Next wipe
- 7d 2h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 60 slots
- Motion · 24 h
- M0.0■steady+0 players
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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 50% of all ranked servers, top 61% in AF. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 7d 2h. The force wipe · high confidence
- wipe-day peak
- 1players, last three wipes
Coming wipes
- 7d 2hThu 5 Nov, 19:00 UTCFW
- 35d 2hThu 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 1, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 1 Oct, 18:03 UTC FW27d ago | M0.0▲rising | 1 | – | running | 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 pageRules and settings
Which map is running on TMR Testing?
The procedural map on TMR Testing is size 3,750 with seed 261001, generated by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.
Which settings and rules apply on TMR Testing?
You will find no gather rate in the name of TMR Testing. At the game's default, groups can have up to 8 players. It plays in survival mode, standard play, with gathering, building and raiding. You can raid and fight other players here. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.
Player counts
What is the current population on TMR Testing?
At this moment, TMR Testing records 0 players across 60 slots. Across seven days this server recorded an average of 0 players and a peak of 1.
How does TMR Testing rank against other Rust servers?
TMR Testing is #19 in Africa and #11,239 worldwide on the past week's player hours, within the top 50% of ranked servers.
Server facts
How reliably does TMR Testing stay online?
Right now, you can reach TMR Testing. Its reported uptime points to a restart about 12 hours ago. Of the 168 hours in the last 7 full days, it was up for 148, or 88% of the time. On 13 September 2026 it was recorded for the first time by Rust Server Trends.
Does TMR Testing hold a steady tick rate?
Its average server fps over the last 48 hours was 83, and it never dropped below 60. At its highest, it carried 83,544 entities: buildings, deployables and the world's other contents. Its highest memory use was 3,019 MB. Lag, as players feel it, comes from fps dropping and the entity count climbing.
Which region does TMR Testing run from?
In Africa TMR Testing lists itself, with the tag AF. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 102.211.186.108:10010 is the address it uses.
Which Rust version is TMR Testing running?
On Linux, TMR Testing runs Rust network protocol 2635 and build 168909. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe schedule
What does wipe day look like on TMR Testing?
On average, the busiest point of its recent wipes drew 1 players. 0 hours after the latest wipe, the crowd peaked.
How often does TMR Testing wipe, and on which days?
The force wipe is the only wipe TMR Testing 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. 27 days 22 hours is how long the current world has been running. Its tags state a monthly wipe schedule.
Tags
What do the server tags on TMR Testing mean?
These are the tags TMR Testing publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp60 (Max players): Slots: 60; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^m (Monthly): It wipes monthly, together with the Facepunch force wipe; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; AF (Africa): The server browser files it under Africa. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does TMR Testing appear?
You will find TMR Testing on the following Rust Server Trends lists: Modded Rust servers, tracked live. These filters bring it up on the server list: Region: Africa; Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
How to join
How do you connect to TMR Testing?
To join, enter client.connect 102.211.186.108:10010 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you. You can find its website at https://TableMountainRust.rusters.io.
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.