Offline 82.66.80.142:28015 checked 29d ago
FluxTest
Connect
srv = rust.server("82.66.80.142: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 23 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 best
Top 71% 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
- 82.66.80.142:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 4 Sep 2026, 14:53 UTC
- hostname
- –
- first seen
- 23 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 · 157 on average | 141/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 127 on average | 125/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 150/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 90 on average | 114/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 35/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 33/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does FluxTest rank?
Player hours over seven days put FluxTest at #16,921, in the top 71% of the ranked set.
How many players does FluxTest hold at once?
Offline now for FluxTest, with the last sample 29 days 20 hours ago.
Server data
Which Rust version is FluxTest on?
The build is Rust network protocol 2633 and build 165217 on Linux, run by FluxTest. The protocol has to match before you can join, and Steam does the updating.
Is FluxTest up, and what does its uptime show?
Offline now for FluxTest, last seen 29 days 20 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 23 September 2026.
Which location does FluxTest run from?
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. 82.66.80.142:28015 is its address.
Rules, settings, map
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, the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Carbon plugins run on it. VAC is running: Valve's anti-cheat is on.
What is the map on FluxTest?
Size 2,000, seed 1337: the procedural map on FluxTest, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe data
When does FluxTest wipe, and on what schedule?
Too few wipes are on record for FluxTest to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 54 days 5 hours ago.
Tags and filters
Which Rust Data filters and lists contain FluxTest?
On Rust Data, FluxTest appears in these lists: 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 FluxTest?
The game's server browser reads these tags from FluxTest: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): 50 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): To join, your game must run protocol 2633; 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): Plugin framework: Carbon. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way into FluxTest?
Enter client.connect 82.66.80.142:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.