Offline 93.115.173.56:28015 checked 27d ago
TableTry TEST
Connect
srv = rust.server("93.115.173.56: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 67% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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
- 93.115.173.56:28015
- region
- –
- max players
- 8
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 10:49 UTC
- hostname
- –
- first seen
- 1 Oct 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 | ShockRust | Blue | NoLimit | no group limit · 150 on average | 77/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 126/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 112/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 40/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 4/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 12/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does TableTry TEST rank?
Rank #15,877 on seven-day player hours for TableTry TEST, within the top 67% of all ranked servers.
What population does TableTry TEST carry?
TableTry TEST returns no live count at this refresh, having last been seen 27 days 19 hours ago.
About the server
Which Rust version is TableTry TEST on?
Rust network protocol 2633 and build 165217 on Windows is what TableTry TEST runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is TableTry TEST, and is it online now?
Offline now for TableTry TEST, last seen 27 days 19 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 1 October 2026.
Where does TableTry TEST sit?
No region is published by TableTry TEST. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 93.115.173.56:28015 is its address.
Rules, settings, map
Which settings and rules does TableTry TEST run?
The name TableTry TEST carries no gather rate. The group limit sits at the default of 8 players. survival is the game mode here, and gather, build, raid: the standard loop. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Carbon plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has TableTry TEST selected?
TableTry TEST runs a procedural map, which the game generates.
Wipes and dates
When does TableTry TEST wipe, and on what schedule?
A rhythm cannot be read from the wipes of TableTry TEST on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 27 days 20 hours ago, and that is the one in play.
Lists and tags
Which lists on Rust Data hold TableTry TEST, and which filters?
These Rust Data lists include TableTry TEST: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the server tags on TableTry TEST?
The game's server browser reads these tags from TableTry TEST: gmrust (Game mode): Survival play, standard Rust; mp8 (Max players): The server lists 8 slots; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): To join, your game must run protocol 2633; cs165217 (Build): Build number: 165217; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Runs on Carbon for plugins. 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.
How to join
What is the way into TableTry TEST?
The manual route: launch Rust, F1, then client.connect 93.115.173.56:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.