Offline 78.17.117.14:28015 checked 3d ago
Test Server
Connect
srv = rust.server("78.17.117.14:28016")
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 10% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. 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 50, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 18 Oct, 08:43 UTC11d ago | 50 | NaN | running | 50 |
| 1 | Wed 7 Oct, 12:09 UTC22d ago | 50 | held half | 10.9 days | 50 |
| 2 | Thu 1 Oct, 19:17 UTC FW27d ago | NaN | NaN | 5.7 days | 50 |
| 3 | Sat 26 Sep, 09:22 UTC33d ago | NaN | NaN | 5.4 days | 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
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 78.17.117.14:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 18 Oct 2026, 08:43 UTC
- hostname
- –
- first seen
- 15 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 | ShockRust | Blue | NoLimit | no group limit · 149 on average | 180/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 177/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 87/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 86 on average | 237/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 86 on average | 233/700 |
Quick answers
From the figures on this page.
Player counts
What position does Test Server take in the server rankings?
Rank #2,126 on seven-day player hours for Test Server, within the top 10% of all ranked servers.
How many players does Test Server hold at once?
Test Server returns no live count at this refresh, having last been seen 3 days 4 hours ago. Over the last seven days it averaged 50 players and peaked at 50.
About the server
Which Rust version is Test Server on?
Version Rust network protocol 2635 and build 168909 on Windows is reported by Test Server. Steam updates your game for you, but the protocol must match to join.
Is Test Server up, and what does its uptime show?
Test Server is offline at this refresh; the last response came 3 days 4 hours ago. Uptime of 4% across the last 7 full days: 7 hours of 168. The first row Rust Data holds for it is dated 15 September 2026.
Which location does Test Server run from?
No region is published by Test Server. Rust Data does not look up where the machine stands; it shows where a server says it is. 78.17.117.14:28015 is its address.
Settings and map
What rules and settings are recorded for Test Server?
No gather rate appears in the name: Test Server. The group limit sits at the default of 8 players. survival is the game mode here, and gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Carbon. Anti-cheat status: VAC off.
Wipe data
On what schedule does Test Server wipe?
Irregular wipe times on Test Server leave no next wipe to forecast. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 11 days 6 hours ago, and that is the one in play.
What is wipe day on Test Server like?
Recent wipes averaged 50 players at their peak. Peak population on the latest wipe came 0 hours in. Recent wipes kept the crowd above half the peak until the next wipe 100% of the time.
Tags and filters
Where does Test Server appear among Rust Data lists and filters?
On Rust Data, Test Server appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks; Players now: At least 50; Average players: 50+ on average.
Which meanings do the tags on Test Server hold?
These tags are published by Test Server and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): Slot count: 50; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Runs on Carbon for plugins. 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 Test Server?
Enter client.connect 78.17.117.14:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.