RUST METRICSFlight deck · live data
Data live Servers11,873 Players96,161 Populated3,898 Fresh wipes 3 h387 Scan5 min
‹ All servers46.225.195.252:28017
Offline Full Queue Fresh wipe Wipe due No query

runonflux.io

Offline 46.225.195.252:28017 checked 28d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 125 250 375 500 PAX 0 /500

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,614top 70%
Last wipe391d 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 Sep24 Sep27 Sep1 Oct4 Oct8 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 timing

How often does runonflux.io wipe, and when?

Its rhythm cannot be told from the wipes of runonflux.io 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 391 days 21 hours ago.

Tags

How should you read the tags on runonflux.io?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp500 (Max players): 500 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2602 (Protocol): Protocol 2602: join only on the same game version; cs133284 (Build): Game build reading: 133284; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set from runonflux.io. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does runonflux.io appear in Rust Metrics lists and filters?

On Rust Metrics, runonflux.io sits in these lists: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

What position does runonflux.io hold among Rust servers?

Ranking for runonflux.io: #16,614 on seven-day player hours, top 70% of all ranked servers.

How full does runonflux.io get?

runonflux.io is not responding; status offline, last seen 28 days 7 hours ago.

Operator and location

Where does runonflux.io sit?

Reading: location. runonflux.io gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 46.225.195.252:28017.

What Rust version is runonflux.io on?

Rust network protocol 2602 and build 133284 on Linux is the build runonflux.io runs. Check: protocol. To join, your game must match; Steam handles the update.

Is runonflux.io up, and how often does it stay up?

Check: connection. runonflux.io is offline at this moment. Last contact was 28 days 7 hours 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 13 September 2026.

Map and rules

What rules does runonflux.io enforce, and what are its settings?

Check: gather rate. The name runonflux.io does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

Which map is live on runonflux.io?

From seed 12345, the game generates the procedural map on runonflux.io. Its size is 3,500. The map repeats when size and seed match. Open it on RustMaps from this page.

Join

What do you do to join runonflux.io?

Check: join. Open Rust, press F1, then enter client.connect 46.225.195.252:28017. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. https://runonflux.com/ is where its website sits.

PLACARDS

Server tags

what each one means

Published as mp500,ptrak,$r?,v2602,gmrust,cs133284,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp500
Max players 500 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2602
Protocol Protocol 2602: join only on the same game version.
cs133284
Build Game build reading: 133284.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

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.