DWG RG-S11186Server sheetchecked 10m ago
TMR Testing
Online AF 102.211.186.108:10010 checked 10m ago
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
Top 50% of all ranked servers, top 55% in AF. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 6d 16h. The force wipe · high confidence
Coming wipes
- 6d 16hThu 5 Nov, 19:00 UTCFW
- 34d 16hThu 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
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 1 Oct, 18:03 UTC FW28d 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
Quick answers
Server details
What uptime is recorded for TMR Testing, and is it up?
Right now, TMR Testing is recorded as online. Counted from its reported uptime, the last restart was about 23 hours ago. For the last 7 full days the record is 148 of 168 hours up, 88% of the time. The first sighting of it by Rust Graphs was on 13 September 2026.
What does the recorded performance of TMR Testing show?
The last 48 hours give an average of 83 server fps and a floor of 60. Counted at its highest: 83,451 entities, buildings, deployables and the rest of the world included. 3,019 MB is the memory peak. Players feel low fps and a climbing entity count as lag.
What location is recorded for TMR Testing?
The AF tag is how TMR Testing lists itself in Africa. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. You will find it at 102.211.186.108:10010.
On which Rust version is TMR Testing running?
The platform is Linux and the version is Rust network protocol 2635 and build 168909 on TMR Testing. The same protocol is required for joining, and Steam updates your game to it.
Population
What does the population history show for TMR Testing?
Current player count on TMR Testing: 0, of 60 slots. Averaged across seven days, the player count is 0, with a peak of 1.
In the rankings, which position does TMR Testing hold?
Across seven days, player hours give TMR Testing #11,186 globally and #17 in Africa, a top 50% position among ranked servers.
Wipe data
What is recorded on TMR Testing on wipe day?
The recent wipes averaged a busiest count of 1 players. At 0 hours after the latest wipe the crowd was at its peak.
On TMR Testing, when do wipes occur?
The force wipe is the only wipe at TMR Testing, once a month. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. 28 days 8 hours ago the current world was made. Its tags give a wipe schedule of one wipe per month.
Rules and settings
Which settings does TMR Testing run, and what rules?
Gather rate for TMR Testing: not stated in the name. No limit is published beyond the default: 8 players per group. It runs the survival game mode, the standard game: gather, build, raid. Raiding and player combat are permitted. The server browser lists it under Modded: plugins or settings change the game. Oxide plugins are run on it. VAC is on: that is Valve's anti-cheat.
What is the map for TMR Testing?
Seed 261001 and size 3,750 define the procedural map TMR Testing generates in game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map.
Tags
Where does TMR Testing appear among the Rust Graphs lists and filters?
The Rust Graphs lists that carry TMR Testing are: Modded Rust servers. It is returned by these filters 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.
On TMR Testing, what is meant by each tag?
The game's server browser reads these tags from TMR Testing: gmrust (Game mode): Standard survival, as Rust plays; mp60 (Max players): Slots: 60; ts8 (Group limit): Teams are capped at 8, the default setting; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): Region code not set; ^m (Monthly): Monthly wipes, on Facepunch's force wipe; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded; AF (Africa): The browser's listing places it under Africa. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
Connect
What is the way to connect to TMR Testing?
Connect with client.connect 102.211.186.108:10010: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you. You will find its website at https://TableMountainRust.rusters.io.
Server tags
Published as mp60,ptrak,$r?,v2635,^m,AF,gmrust,cs168909,ts8,^o^z
Game
gmrust
mp60
ts8
v2635
cs168909
ptrak
$r?
Wipe schedule
^m
Mods and access
^o
^z
Region
AF
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.