RUST METRICSFlight deck · live data
Data live Servers11,615 Players36,116 Populated2,895 Fresh wipes 3 h67 Scan5 min
‹ All servers5.182.207.231:11000
Online Full Queue Fresh wipe Wipe due No query

TESTTTTT

Online 5.182.207.231:11000 checked 11m ago

biweekly wipes moddedoxidepvehardcore
COM 1 · connect

Server instruments

last reading Thu 05:00 UTC
0 0.2 0.5 0.8 1 PAX 0 /?

Players now

no slots published 7-day avg7-day peak 1, past the slots
0 10 30 60 120 256 FPS 290 SERVER FPS

Server fps

48 h low 184 · below 20 is lag, below 10 is bad
0 150 300 450 600 ENT 368,980 ×1000

Entities

48 h range 367,236–371,443 · memory 8,527 MB
1239 ET SINCE RESTART 2D 23H

Uptime

2 days 23 hours since its last restart, at the last reading
7-day average0peak 1
Rank#5,391top 24%
Last wipe27d agobiweekly schedule
Next wipe7d 11hThu 5 Nov, 19:00 UTC FW
Memory8,527MB48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75108:0017:0002:0010:0020:0005:00

Hourly average and peak, UTC.

REC 2

Server performance

010020030040008:0017:0002:0010:0020:0005:00

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
12.5k5k7.5k10k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

PLAN

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 7d 11h. The force wipe · high confidence

usual gap2 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak1players, last three wipes
crowd held50%else halves by day 1

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC7d 11hFW
  2. WPT 2Sat 7 Nov, 19:22 UTC9d 12h
  3. WPT 3Sat 21 Nov, 19:22 UTC23d 12h
  4. WPT 4Thu 3 Dec, 19:00 UTC35d 11hFW
  5. WPT 5Sat 5 Dec, 19:22 UTC37d 12h

The first 48 hours of its last wipes

Sat 10 OctThu 1 OctTue 29 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, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 10 Oct, 19:22 UTC18d ago 1 – running 1
Thu 1 Oct, 18:23 UTC FW27d ago 1 halved by day 1 9 days 0
Tue 29 Sep, 17:59 UTC29d ago 1 held half 2 days 0
Mon 28 Sep, 19:01 UTC30d ago 1 – 1 days 0

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 TESTTTTT when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe. Above half that peak the crowd stayed until the next wipe in 50% of recent wipes. By day 1 it fell below half when it didn't.

What wipe timing does TESTTTTT follow?

Its tag guides the prediction: too few of TESTTTTT's wipes are on record to confirm its schedule. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. The world in play was created 27 days 13 hours ago. A wipe schedule of every two weeks is published in its tags.

Tags

How should you read the tags on TESTTTTT?

Tags published by TESTTTTT, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp0 (Max players): 0 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^b (Biweekly): Check: wipe cycle. Every two weeks; ^h (Hardcore): Hardcore mode, as Facepunch defines it: less help, tougher survival; ^p (PvE): Check: mode. PvE, so the world supplies the danger, not other players; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Plugins or settings make this a modded server. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does TESTTTTT appear in Rust Metrics lists and filters?

On Rust Metrics, TESTTTTT sits in these lists: Modded Rust servers, checked live and Rust PvE servers. Reading: server list filters. It comes up under Type: Modded; Game mode: PvE and Hardcore; Server tag: Biweekly ^b, Hardcore ^h, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.

Player count

Where does TESTTTTT sit in the rankings?

Ranking for TESTTTTT: #5,391 on seven-day player hours, top 24% of all ranked servers.

What player count does TESTTTTT carry?

Reading for TESTTTTT: 0 players online now. Seven-day check: 0 players on average. Peak reading: 1. The last 48 hours peaked at 10:00 UTC, averaging 1 players at that hour.

Operator and location

What location is TESTTTTT hosted in?

Reading: location. TESTTTTT gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 5.182.207.231:11000.

What Rust version is TESTTTTT on?

Version check: Rust network protocol 2635 and build 168909 on Windows, run by TESTTTTT. Matching protocol is required to join. Let Steam update your game.

What is the performance reading for TESTTTTT?

Check: fps. Average 299 server fps over the last 48 hours, low of 184. Within range. Peak entity count: 371,443. Buildings, deployables and all else included. Check: memory. Peak use was 9,874 MB. What players call lag comes from low fps and an entity count on the rise.

How reliable is TESTTTTT, and is it online now?

Reading: online. TESTTTTT answers right now. Check: restart. The uptime it reports puts the last restart about 2 days 23 hours ago. Uptime for the last 7 full days: 167 of 168 hours, or 99%. The first sighting on Rust Metrics was 13 September 2026.

Settings and map

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

No gather rate appears in the name: TESTTTTT. 8 players per group, the default value. Mode check gives hardcore; Facepunch's most punishing mode. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.

Which map is live on TESTTTTT?

From seed 2234235, the game generates the procedural map on TESTTTTT. Its size is 4,500. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page. Its map carries the name Custom Map.

How to join

How do you connect to TESTTTTT?

To join: start Rust, press F1 and type client.connect 5.182.207.231:11000. Or press Launch Rust here and Steam opens the game and connects you. You can find its website at https://rust-z.gamestores.app/.

PLACARDS

Server tags

what each one means

Published as mp0,ptrak,$r?,v2635,^b,^h,^p,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp0
Max players 0 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Wipe schedule

^b
Biweekly Check: wipe cycle. Every two weeks.

Difficulty

^h
Hardcore Hardcore mode, as Facepunch defines it: less help, tougher survival.

Gameplay

^p
PvE Check: mode. PvE, so the world supplies the danger, not other players.

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.