Offline 83.202.36.141:28115 checked 3d ago
RTM Local Test
Connect
srv = rust.server("83.202.36.141:28117")
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. 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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly 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 | Sun 18 Oct, 14:04 UTC10d 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 83.202.36.141:28115
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 18 Oct 2026, 14:04 UTC
- hostname
- –
- first seen
- 13 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 560 on average | 173/250 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 119/200 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 18/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 288 on average | 13/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 274 on average | 19/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 250 on average | 23/225 |
Quick answers
From the figures on this page.
Player counts
How does RTM Local Test compare in the rankings?
Rank #15,353 on seven-day player hours for RTM Local Test, within the top 69% of all ranked servers.
How many players does RTM Local Test hold at once?
Offline now for RTM Local Test, with the last sample 3 days 3 hours ago. Over the last seven days it averaged 0 players.
Server facts
What Rust version does RTM Local Test run?
Rust network protocol 2634 and build 167781 on Windows is what RTM Local Test runs. The protocol has to match before you can join, and Steam does the updating.
Is RTM Local Test up, and what does its uptime show?
RTM Local Test is offline at this refresh; the last response came 3 days 3 hours ago. 5 of 168 hours up over the last 7 full days, or 3%. Rust Data logged it first on 13 September 2026.
In which location is RTM Local Test hosted?
For RTM Local Test, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 83.202.36.141:28115.
Settings and map
What rules and settings are recorded for RTM Local Test?
The name RTM Local Test carries no gather rate. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. The server browser lists it under Community. Anti-cheat status: VAC on.
Which map has RTM Local Test selected?
RTM Local Test runs a procedural map, which the game generates.
Wipe data
When does RTM Local Test wipe, and on what schedule?
Too few wipes are on record for RTM Local Test to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 10 days 11 hours ago.
What is wipe day on RTM Local Test like?
Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags, lists
Which lists on Rust Data hold RTM Local Test, and which filters?
On Rust Data, RTM Local Test appears in these lists: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the server tags on RTM Local Test?
Read by the game's server browser, the tags RTM Local Test publishes are: gmrust (Game mode): Survival play, standard Rust; mp2 (Max players): 2 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): Build number: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way into RTM Local Test?
In Rust, F1 opens the console: type client.connect 83.202.36.141:28115. Launch Rust on this page does the same by opening the game through Steam and connecting.