Online AF 102.211.186.108:10010 checked 12m ago
TMR Testing
Connect
srv = rust.server("102.211.186.108:10020")
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, measured since 17 Sep. 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 best
Top 50% of all ranked servers, top 63% in AF. 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 3h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 3h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 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
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 18:03 UTC FW27d ago | 1 | NaN | 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.
display(srv.map, srv.info())
Map
3750 · seed 261001
- map
- Procedural Map
- size
- 3750
- seed
- 261001
Server
srv.info()- address
- 102.211.186.108:10010
- region
- AF
- max players
- 60
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 1 Oct 2026, 18:03 UTC
- hostname
- –
- first seen
- 13 Sep 2026
About this server · in its own words
print(srv.description)
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | Intoxicated ZA Vanilla 3 - 01 Oct | AF · groups of 8+ · monthly · 18 on average | 13/150 |
| 1 | ServerZ Rust Monthly ZA | AF · groups of 8+ · monthly · 1 on average | 0/50 |
| 2 | Voodoo ZA | AF · groups of 8+ · monthly · 1 on average | 0/100 |
| 3 | Intoxicated ZA Vanilla 1 - Wipe soon | AF · groups of 8+ · biweekly · 7 on average | 10/100 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 91/700 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 86 on average | 236/700 |
Quick answers
From the figures on this page.
Population data
How does TMR Testing compare in the rankings?
On seven-day player hours TMR Testing is #11,221 overall and #19 in Africa, inside the top 50% of all ranked servers.
How full does TMR Testing run?
The sample now reads 0 players for TMR Testing, out of 60 slots. Over the last seven days it averaged 0 players and peaked at 1.
About the server
How well does TMR Testing perform?
Server fps over the last 48 hours averages 84; the floor is 60. Buildings, deployables and all else in the world took the count as high as 83,544 entities. The memory field tops out at 3,019 MB. Low fps plus an entity count on the way up is the lag players report.
What Rust version does TMR Testing run?
Version Rust network protocol 2635 and build 168909 on Linux is reported by TMR Testing. Steam updates your game for you, but the protocol must match to join.
Is TMR Testing up, and what does its uptime show?
TMR Testing reports itself online at the current refresh. Count back 10 hours from its reported uptime to get the last restart. 148 of 168 hours up over the last 7 full days, or 88%. Its earliest recorded date in Rust Data is 13 September 2026.
Which location does TMR Testing run from?
The AF tag is what TMR Testing uses to list itself in Africa. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 102.211.186.108:10010 is its address.
Map and rules
Which rules apply on TMR Testing, and what settings?
You will not find a gather rate in the string TMR Testing. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
Which map has TMR Testing loaded?
Size 3,750, seed 261001: the procedural map on TMR Testing, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipes and dates
When does TMR Testing wipe, and on what schedule?
Once a month TMR Testing wipes, with the force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. A new world was started 27 days 21 hours ago, and that is the one in play. Its tags carry a monthly wipe schedule.
What is wipe day on TMR Testing like?
Recent wipes averaged 1 players at their peak. 0 hours after the latest wipe, the crowd reached its peak.
Lists and tags
Which lists on Rust Data hold TMR Testing, and which filters?
The Rust Data lists that TMR Testing fits are: Modded Rust servers. 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 should you read the server tags on TMR Testing?
Read by the game's server browser, the tags TMR Testing publishes are: gmrust (Game mode): Survival play, standard Rust; mp60 (Max players): Slot count: 60; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^m (Monthly): Monthly: the wipe lands with Facepunch's force wipe; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; AF (Africa): The server browser files it under Africa. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
How can I connect to TMR Testing?
Enter client.connect 102.211.186.108:10010 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. You will find its website at https://TableMountainRust.rusters.io.
