RUST METRICSFlight deck · live data
Data live Servers11,701 Players46,298 Populated3,163 Fresh wipes 3 h102 Scan5 min
‹ All servers82.66.80.142:28015
Offline Full Queue Fresh wipe Wipe due No query

FluxTest

Offline 82.66.80.142:28015 checked 30d ago

moddedcarbon
COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#16,921top 71%
Last wipe54d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k23 Sep25 Sep28 Sep30 Sep3 Oct5 Oct

Top 71% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

How often does FluxTest wipe, and when?

To tell the rhythm of FluxTest, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 54 days 9 hours ago.

Lists and filters

Which tags does FluxTest carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): Game build reading: 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Carbon handles the plugins here from FluxTest. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show FluxTest?

On Rust Metrics, FluxTest sits in these lists: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Occupancy

Where does FluxTest sit in the rankings?

Player hours over seven days put FluxTest at #16,921, in the top 71% of all ranked servers.

What is the population on FluxTest?

Status for FluxTest: offline. Last seen 30 days ago.

Server details

Which location does FluxTest run from?

No region tag on FluxTest. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 82.66.80.142:28015.

What Rust version is FluxTest on?

Version check: Rust network protocol 2633 and build 165217 on Linux, run by FluxTest. To get in, your game needs the same protocol; Steam applies the update.

Is FluxTest up, and how often does it stay up?

FluxTest reports offline. The last reading came 30 days ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 23 September 2026.

Settings and map

What rules does FluxTest enforce, and what are its settings?

Reading the name gives no gather rate for FluxTest. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Carbon of them. Anti-cheat reading: VAC on, Valve's system.

Which map is live on FluxTest?

Check: map. Procedural, size 2,000, seed 1337, generated by the game on FluxTest. View it on RustMaps from this page: matching size and seed give an identical map.

How to join

How can you get onto FluxTest?

Press F1 in Rust and enter client.connect 82.66.80.142:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2633,gmrust,cs165217,ts8,^z,^y

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players The server holds 50 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Match the game version: protocol 2633 is required.
cs165217
Build Game build reading: 165217.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Mods and access

^z
Modded Check: category. Modded, because plugins or settings alter the game.
^y
Carbon Carbon handles the plugins here.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.