Offline 185.17.103.182:28015 checked 29d ago
FluxTest
Connect
srv = rust.server("185.17.103.182: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, measured since 17 Sep. 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 70% 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
2000 · seed 1337
- map
- Procedural Map
- size
- 2000
- seed
- 1337
Server
srv.info()- address
- 185.17.103.182:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 4 Sep 2026, 14:53 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 | ShockRust | Blue | NoLimit | no group limit · 150 on average | 99/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 123/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 118/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 44/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 | 20/1000 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does FluxTest rank?
Player hours over seven days put FluxTest at #16,837, in the top 70% of the ranked set.
How full does FluxTest run?
The current row shows FluxTest offline; the last response was 29 days 4 hours ago.
Server facts
What Rust version does FluxTest run?
Rust network protocol 2633 and build 165217 on Linux is what FluxTest runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is FluxTest, and is it up?
The latest sample has FluxTest offline, with a last sighting 29 days 4 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 13 September 2026.
Where does FluxTest sit?
No region is published by FluxTest. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 185.17.103.182:28015.
Map and rules
What rules and settings are recorded for FluxTest?
You will not find a gather rate in the string FluxTest. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. 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.
Which map has FluxTest selected?
Size 2,000, seed 1337: the procedural map on FluxTest, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe schedule
When does FluxTest wipe, and how often?
The record for FluxTest holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 54 days 17 hours ago, and that is the one in play.
Lists and tags
Which lists on Rust Data hold FluxTest, and which filters?
The Rust Data lists that FluxTest fits are: 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.
How should you read the server tags on FluxTest?
These tags are published by FluxTest and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs165217 (Build): The server runs build 165217; ptrak (Networking): Standard network layer for Rust: RakNet; $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
How can I connect to FluxTest?
The manual route: launch Rust, F1, then client.connect 185.17.103.182:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.