Offline 47.12.3.82:28015 checked 30d ago
Ts Testing server
Connect
srv = rust.server("47.12.3.82:28017")
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 61% 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 27 Sep, 21:32 UTC30d 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
- 47.12.3.82:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 27 Sep 2026, 21:43 UTC
- hostname
- –
- first seen
- 27 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 · 533 on average | 241/275 |
| 1 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 325 on average | 14/250 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 323 on average | 21/250 |
| 3 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 318 on average | 155/200 |
| 4 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 278 on average | 60/200 |
| 5 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 264 on average | 32/100 |
Quick answers
From the figures on this page.
Population data
How does Ts Testing server compare in the rankings?
Over the last seven days Ts Testing server sits at #14,544 on player hours, in the top 61% of ranked servers.
What population does Ts Testing server carry?
Ts Testing server returns no live count at this refresh, having last been seen 30 days 2 hours ago.
Server data
What Rust version does Ts Testing server run?
Rust network protocol 2633 and build 165217 on Windows is what Ts Testing server runs. Joining needs the same protocol on your game; Steam handles the update.
Is Ts Testing server up, and what does its uptime show?
Ts Testing server is offline at this refresh; the last response came 30 days 2 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 27 September 2026.
In which location is Ts Testing server hosted?
For Ts Testing server, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 47.12.3.82:28015 is its address.
Map and rules
Which rules apply on Ts Testing server, and what settings?
The name Ts Testing server carries no gather rate. No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Fighting and raiding between players are allowed. The server browser lists it under Community. Anti-cheat status: VAC on.
Which map has Ts Testing server loaded?
The game generates its map: procedural, on Ts Testing server.
Wipe schedule
When does Ts Testing server wipe, and on what schedule?
Too few wipes are on record for Ts Testing server 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 30 days 7 hours ago.
On Ts Testing server, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Which lists on Rust Data hold Ts Testing server, and which filters?
On Rust Data, Ts Testing server appears in these lists: Rust community servers, unfiltered. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Which meanings do the tags on Ts Testing server hold?
The game's server browser reads these tags from Ts Testing server: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): 1 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs165217 (Build): Recorded game build: 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
What is the way to join Ts Testing server?
The manual route: launch Rust, F1, then client.connect 47.12.3.82:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.