Offline 143.14.123.180:28015 checked 27d ago
TableTry TEST
Connect
srv = rust.server("143.14.123.180: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 bestTop 69% of all ranked servers. 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 0h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 0h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 0h | 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 19:52 UTC FW27d ago | 0 | NaN | running | 1 |
# 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
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 143.14.123.180:28015
- region
- –
- max players
- 8
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 19:52 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 · 151 on average | 120/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 120/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 197/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 95 on average | 75/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 89 on average | 228/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 348/350 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does TableTry TEST rank?
Over the last seven days TableTry TEST sits at #16,036 on player hours, in the top 69% of ranked servers.
How many players does TableTry TEST hold at once?
The current row shows TableTry TEST offline; the last response was 27 days 22 hours ago.
Server data
What is the Rust version on TableTry TEST?
The build is Rust network protocol 2634 and build 166494 on Windows, run by TableTry TEST. Steam updates your game for you, but the protocol must match to join.
How reliable is TableTry TEST, and is it up?
TableTry TEST is offline at this refresh; the last response came 27 days 22 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 1 October 2026.
In which location is TableTry TEST hosted?
There is no region published for TableTry TEST. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 143.14.123.180:28015.
Rules, settings, map
Which settings and rules does TableTry TEST run?
You will not find a gather rate in the string TableTry TEST. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Carbon plugins run on it. VAC, Valve's anti-cheat, is enabled.
Wipes and dates
When does TableTry TEST wipe, and how often?
Once a month TableTry TEST wipes, with the force wipe. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. A new world was started 27 days 22 hours ago, and that is the one in play.
What is wipe day on TableTry TEST like?
Across recent wipes the busiest point averaged 0 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags and filters
Where does TableTry TEST appear among Rust Data lists and filters?
These Rust Data lists include TableTry TEST: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Which meanings do the tags on TableTry TEST hold?
These tags are published by TableTry TEST and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp8 (Max players): 8 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs166494 (Build): Recorded game build: 166494; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way into TableTry TEST?
In Rust, F1 opens the console: type client.connect 143.14.123.180:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.