RUST METRICSFlight deck · live data
Data live Servers11,844 Players83,167 Populated3,755 Fresh wipes 3 h280 Scan5 min
‹ All servers104.28.218.149:28025
Offline Full Queue Fresh wipe Wipe due No query

MixMods Test (oxide)

Offline 104.28.218.149:28025 checked 20d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 1 2 3 4 PAX 0 /4

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#15,853top 72%
Last wipe22d 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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k9 Oct10 Oct12 Oct13 Oct15 Oct16 Oct

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

What wipe timing does MixMods Test (oxide) follow?

Its rhythm cannot be told from the wipes of MixMods Test (oxide) 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 22 days 5 hours ago.

Tags

How should you read the tags on MixMods Test (oxide)?

Tags published by MixMods Test (oxide), read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp4 (Max players): The server holds 4 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166652 (Build): Build 166652; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Plugins or settings make this a modded server. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does MixMods Test (oxide) appear in Rust Metrics lists and filters?

On Rust Metrics, MixMods Test (oxide) sits in these lists: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Population

Where does MixMods Test (oxide) sit in the rankings?

Ranking for MixMods Test (oxide): #15,853 on seven-day player hours, top 72% of all ranked servers.

What is the population on MixMods Test (oxide)?

Reading for MixMods Test (oxide): offline at this moment; last seen 20 days 7 hours ago.

Operator and location

Which location does MixMods Test (oxide) run from?

Reading: location. MixMods Test (oxide) gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 104.28.218.149:28025.

What Rust version is MixMods Test (oxide) on?

Version check: Rust network protocol 2634 and build 166652 on Linux, run by MixMods Test (oxide). Matching protocol is required to join. Let Steam update your game.

How reliable is MixMods Test (oxide), and is it online now?

Reading: offline. MixMods Test (oxide) last answered 20 days 7 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 9 October 2026.

Map and rules

How is MixMods Test (oxide) configured, and what rules are in force?

Check: gather rate. The name MixMods Test (oxide) does not state one. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on MixMods Test (oxide)?

Check: map. Procedural, generated by the game, on MixMods Test (oxide).

Connection

How can you get onto MixMods Test (oxide)?

Check: join. Open Rust, press F1, then enter client.connect 104.28.218.149:28025. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp4,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp4
Max players The server holds 4 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166652
Build Build 166652.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Plugins or settings make this a modded server.

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.