RUST METRICSFlight deck · live data
Data live Servers11,793 Players79,700 Populated3,567 Fresh wipes 3 h247 Scan5 min
‹ All servers203.123.106.109:28015
Offline Full Queue Fresh wipe Wipe due No query

qualityfarts

Offline 203.123.106.109:28015 checked 33d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 1 /10

Players now

10% 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#14,351top 61%
Last wipe33d agono schedule published
Next wipe–too few wipes 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
15k10k15k20k25 Sep27 Sep28 Sep30 Sep1 Oct3 Oct

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

PLAN

Wipe schedule

too few wipes seen yet

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

usual gap1.2 daysbetween real wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Sat 26 SepFri 25 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 26 Sep, 17:34 UTC33d ago 1 – running 1
Fri 25 Sep, 11:34 UTC34d ago 1 – 1.2 days 1

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

What happens on qualityfarts when wipe day comes?

The busiest point of its recent wipes drew 1 players on average. 1 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does qualityfarts follow?

To tell the rhythm of qualityfarts, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 33 days 4 hours ago the current world was made.

Lists and filters

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

These are the tags qualityfarts publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): The server runs game build 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does qualityfarts appear in Rust Metrics lists and filters?

On Rust Metrics, qualityfarts sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

What position does qualityfarts hold among Rust servers?

Ranking for qualityfarts: #14,351 on seven-day player hours, top 61% of all ranked servers.

What player count does qualityfarts carry?

Status for qualityfarts: offline. Last seen 33 days 1 hours ago.

Server

What location is qualityfarts hosted in?

Reading: location. qualityfarts gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 203.123.106.109:28015.

What Rust version is qualityfarts on?

Reading: qualityfarts, Rust network protocol 2633 and build 165217, Windows. To get in, your game needs the same protocol; Steam applies the update.

How reliable is qualityfarts, and is it online now?

qualityfarts reports offline. The last reading came 33 days 1 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 25 September 2026, recorded by Rust Metrics.

Map and rules

How is qualityfarts configured, and what rules are in force?

Reading the name gives no gather rate for qualityfarts. The group cap is 8 players, which is the default in the game. 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: Community server. Check: anti-cheat. VAC, Valve's system, is on.

What map is qualityfarts on?

Procedural map on qualityfarts, made by the game's generator.

How to join

How do you connect to qualityfarts?

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

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players Slots: 10.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build The server runs game build 165217.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.