RUST METRICSFlight deck · live data
Data live Servers11,636 Players31,247 Populated2,768 Fresh wipes 3 h72 Scan5 min
‹ All servers185.17.103.182:28015
Offline Full Queue Fresh wipe Wipe due No query

FluxTest

Offline 185.17.103.182:28015 checked 29d 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,837top 70%
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 17 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
15k10k15k20k20 Sep23 Sep27 Sep30 Sep4 Oct7 Oct

Top 70% 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

Wipe schedule

When does FluxTest wipe?

Its rhythm cannot be told from the wipes of FluxTest on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 54 days 14 hours ago.

Tags

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

These are the tags FluxTest publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): 50 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): Build 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Check: framework. Carbon. 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?

Rust Metrics lists featuring FluxTest: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Player count

What position does FluxTest hold among Rust servers?

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

What is the population on FluxTest?

FluxTest is not responding; status offline, last seen 29 days 2 hours 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. Connect using 185.17.103.182:28015.

What Rust version is FluxTest on?

Version check: Rust network protocol 2633 and build 165217 on Linux, run by FluxTest. Check: protocol. To join, your game must match; Steam handles the update.

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

Reading: offline. FluxTest last answered 29 days 2 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

What settings and rules apply on FluxTest?

Check: gather rate. The name FluxTest does not state one. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Carbon of them. Anti-cheat reading: VAC on, Valve's system.

What map is FluxTest on?

From seed 1337, the game generates the procedural map on FluxTest. Its size is 2,000. The map repeats when size and seed match. Open it on RustMaps from this page.

Connection

How can you get onto FluxTest?

Press F1 in Rust and enter client.connect 185.17.103.182: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 50 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Match the game version: protocol 2633 is required.
cs165217
Build Build 165217.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Mods and access

^z
Modded Modded: plugins or settings depart from the stock game.
^y
Carbon Check: framework. Carbon.

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.