TMR Testing
Online AF 102.211.186.108:10010 checked 9m ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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 63% 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 3h. The force wipe · high confidence
Coming wipes
| In | When, UTC | Kind |
|---|---|---|
| 7d 3h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 35d 3h | 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 1, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 1 Oct, 18:03 UTC FW27d ago | 1 | – | running | 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| Server | Profile | Players now |
|---|---|---|
| Intoxicated ZA Vanilla 3 - 01 Oct | AF · groups of 8+ · monthly · 18 on average | 11 / 150 |
| ServerZ Rust Monthly ZA | AF · groups of 8+ · monthly · 1 on average | 0 / 50 |
| Voodoo ZA | AF · groups of 8+ · monthly · 1 on average | 0 / 100 |
| Intoxicated ZA Vanilla 1 - Wipe soon | AF · groups of 8+ · biweekly · 7 on average | 16 / 100 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 85 / 700 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 86 on average | 246 / 700 |
Quick answers
from the figures on this pageWipe data
When does TMR Testing wipe?
With the force wipe, once a month, TMR Testing wipes. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. The world now in play was created 27 days 21 hours ago. The tags carry a monthly wipe schedule.
On TMR Testing, what happens on wipe day?
Recent wipes averaged a busiest count of 1 players. Peak population for the latest wipe came 0 hours after it began.
Server details
What is the hosting location of TMR Testing?
In Africa, according to its AF tag, sits TMR Testing. Where a server says it is, that is what Rust Server Analytics shows, without looking up where the machine stands. The address of the server is 102.211.186.108:10010.
Which Rust version is TMR Testing on?
On Linux, TMR Testing runs Rust network protocol 2635 and build 168909. Your game must match the protocol to join, and Steam applies that update.
Is TMR Testing up, and how steady is its uptime?
As of the latest refresh, TMR Testing is online. About 11 hours ago is when it last restarted, judged by its reported uptime. Uptime over the last full days (7) was 88%, or 148 of 168 hours. It entered Rust Server Analytics records on 13 September 2026.
Does TMR Testing perform well?
The 48-hour average was 84 server fps; the low was 60. Buildings, deployables and all other world objects brought the entity total to 83,544. Memory use reached 3,019 MB at peak. Lag, for players, means low fps alongside a growing entity count.
Lists and tags
Which meanings do the tags on TMR Testing carry?
The game's server browser reads the tags TMR Testing publishes: gmrust (Game mode): Survival in the standard Rust format; mp60 (Max players): Capacity of 60 slots; ts8 (Group limit): Team cap of 8, the stock game setting; v2635 (Protocol): Protocol 2635 is required: your game must match to connect; cs168909 (Build): Build number 168909; ptrak (Networking): RakNet is the network layer, the game's standard one; $r? (Region code): No region code has been set; ^m (Monthly): The wipe cycle is monthly and follows Facepunch's force wipe; ^o (Oxide): It runs Oxide (uMod) for plugins; ^z (Modded): The Modded section, because plugins or settings modify play; AF (Africa): Its browser listing sits in Africa. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.
Where does TMR Testing appear across Rust Server Analytics's lists and filters?
The following Rust Server Analytics lists count TMR Testing among their servers: Modded Rust servers: live data. On the server list, the filters that return it are: Region: Africa; Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Player numbers
What position does TMR Testing hold in the server rankings?
For player hours over the last seven days, TMR Testing places #11,221 globally and #19 in Africa, in the top 50% of all ranked servers.
How many players does TMR Testing carry?
Of 60 slots, 0 are filled on TMR Testing at this refresh. The seven-day mean is 0 players, against a peak of 1.
Map and rules
What settings and rules does TMR Testing use?
No gather rate is given in the name of TMR Testing. The game's default 8-player group limit is in force. It runs survival, the standard game: gather, build, raid. Player-versus-player combat and raiding are both enabled. Plugins or settings modify the game, and it is listed as Modded. Plugins from Oxide are in use. VAC, Valve's anti-cheat, is enabled.
The map on TMR Testing: which one is it?
The game generates a procedural map of size 3,750 with seed 261001 for TMR Testing. Size and seed fix the map, so a RustMaps view is available from this page.
How to join
How do you connect to TMR Testing?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 102.211.186.108:10010. https://TableMountainRust.rusters.io is its website.