RUST METRICSFlight deck · live data
Data live Servers11,665 Players33,246 Populated2,811 Fresh wipes 3 h81 Scan5 min
‹ All servers141.105.66.97:28015
Offline Full Queue Fresh wipe Wipe due No query

R3D Fixtest 1650312773 / 4500

Offline 141.105.66.97:28015 checked 45d ago

COM 1 · connect

Server instruments

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

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–score 0
Last wipe45d 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
No rank history yet.
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

What wipe timing does R3D Fixtest 1650312773 / 4500 follow?

Its rhythm cannot be told from the wipes of R3D Fixtest 1650312773 / 4500 on record: there are too few. 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 45 days 16 hours ago.

Lists and filters

How should you read the tags on R3D Fixtest 1650312773 / 4500?

Tags published by R3D Fixtest 1650312773 / 4500, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163110 (Build): Game build reading: 163110; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show R3D Fixtest 1650312773 / 4500?

These Rust Metrics lists carry R3D Fixtest 1650312773 / 4500: 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.

Population

What is the population on R3D Fixtest 1650312773 / 4500?

Status for R3D Fixtest 1650312773 / 4500: offline. Last seen 45 days 16 hours ago.

Server

Where does R3D Fixtest 1650312773 / 4500 sit?

Reading: location. R3D Fixtest 1650312773 / 4500 gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 141.105.66.97:28015.

What Rust version is R3D Fixtest 1650312773 / 4500 on?

Reading: R3D Fixtest 1650312773 / 4500, Rust network protocol 2633 and build 163110, Linux. To get in, your game needs the same protocol; Steam applies the update.

Is R3D Fixtest 1650312773 / 4500 up, and how often does it stay up?

Check: connection. R3D Fixtest 1650312773 / 4500 is offline at this moment. Last contact was 45 days 16 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 13 September 2026.

Settings and map

What settings and rules apply on R3D Fixtest 1650312773 / 4500?

Reading the name gives no gather rate for R3D Fixtest 1650312773 / 4500. 8 players per group, the default value. 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.

Join

How do you connect to R3D Fixtest 1650312773 / 4500?

Check: join. Open Rust, press F1, then enter client.connect 141.105.66.97: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,cs163110,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players Slots: 10.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Your game must run protocol 2633 to get in.
cs163110
Build Game build reading: 163110.
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.