Rust Player Count
84,498 playing now

Online5.182.207.231:11000checked 12m ago

TESTTTTT

biweekly wipes moddedoxidepvehardcore
Players now 0/ ?
7-day average 0 peak 1
Rank #8,754 top 39%
Last wipe 12d ago biweekly schedule
Next wipe 10d 2h Sat 24 Oct, 19:22 UTC

Players

AveragePeak
00.250.50.75117:0002:0011:0021:0006:0015:00

Hourly average and peak, UTC.

Server performance

010020030040017:0002:0011:0021:0006:0015: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.

Rank

daily · 1 is best
RankRank in region
12.5k5k7.5k10k20 Sep25 Sep30 Sep4 Oct9 Oct14 Oct

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

Wipe schedule

from its schedule tag

Next wipe Saturday 24 October, 19:22 UTC, in 10d 2h. Its biweekly schedule tag · low confidence

Usual gap 2 days between real wipes
On rhythm 33% of its recent wipes
Wipe-day peak 1 players, last three wipes
Crowd held 50% else halves by day 1

Coming wipes

10d 2hSat 24 Oct, 19:22 UTC
22d 2hThu 5 Nov, 19:00 UTC FW
24d 2hSat 7 Nov, 19:22 UTC
38d 2hSat 21 Nov, 19:22 UTC

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.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 10 Oct, 19:22 UTC3d ago 1 – running 1
Thu 1 Oct, 18:23 UTC FW12d ago 1 halved by day 1 9 days 0
Tue 29 Sep, 17:59 UTC14d ago 1 held half 2 days 0
Mon 28 Sep, 19:01 UTC15d 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
Alias RPG Season 10 [PVE,RU]EU · groups of 8+ · biweekly · 10 on average 15/ 100
RustNK - Custom Hardcore PvE, NPCs, Events & QuestsNA · no group limit · biweekly · 5 on average 3/ 50
HARD PVE TOP | Classic PvE | RaidBases | Custom Events | No VIPgroups of 8+ · biweekly · 4 on average 12/ 50
RustAria#1 [PvE/QUEST/RPG/CRAFT/HARD]groups of 50+ · biweekly · 2 on average 2/ 200
#2 RUSTMAX PVE HARD x1/ZOMBIE/BASE/EVENTSEU · no group limit · 1x · biweekly · 2 on average 0/ 50
[EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoEU · no group limit · biweekly · 203 on average 229/ 2000

Quick answers

from the figures on this page

Rules and settings

Which rules govern TESTTTTT?

A gather rate is absent from the name of TESTTTTT. Up to 8 players per group, which is the game's default. The server runs hardcore, The hardest mode from Facepunch. You can fight and raid other players. You will find it in the Modded section: the game is changed by plugins or settings. Oxide plugins are running on it. VAC is on, Valve's anti-cheat.

Which map is running on TESTTTTT?

The game generates a procedural map of size 4,500 with seed 2234235 for TESTTTTT. You can see it on RustMaps from this page, because the same size and seed give the same map. Its map is called: Custom Map.

Tags and filters

Where can TESTTTTT be found in Rust Player Count lists and filters?

The Rust Player Count lists that TESTTTTT fits are: Modded Rust servers and Rust PvE servers. You can find it on the server list using these filters: 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; Last wipe: In the last 2 weeks.

What information do the tags on TESTTTTT convey?

The game's server browser reads these tags from TESTTTTT: gmrust (Game mode): The usual Rust survival experience; mp0 (Max players): 0 slots are available; ts8 (Group limit): This uses the default team cap: 8 players; v2634 (Protocol): Your game version needs to be on protocol 2634 to connect; cs167398 (Build): It runs on game build 167398; ptrak (Networking): It uses RakNet, the game's default networking; $r? (Region code): The region code field is empty; ^b (Biweekly): The server wipes on a two-week cycle; ^h (Hardcore): Hardcore mode from Facepunch: survival is harder and help is scarcer; ^p (PvE): No player-versus-player combat: the environment provides the danger; ^o (Oxide): The plugin framework Oxide (uMod) is in use; ^z (Modded): It appears under Modded because plugins or settings modify the game. At the top of this page, its tags show its current players, queue and world creation time as well.

Player numbers

What is the player count on TESTTTTT?

TESTTTTT currently has 0 players. With a peak of 1, the average over seven days is 0 players. The highest average in the last 48 hours was 1 players at 20:00 UTC.

Where does TESTTTTT sit in the rankings?

For player hours in the last seven days, TESTTTTT ranks #8,754 and is in the top 39% of all ranked servers.

Server details

What is the uptime and reliability of TESTTTTT?

TESTTTTT is currently online. The uptime it gives suggests it restarted about 3 days 19 hours ago. In the last 7 full days, it was up for 168 of 168 hours, which is 100% uptime. 13 September 2026 is when Rust Player Count first saw it.

What Rust version is used on TESTTTTT?

On Windows, TESTTTTT runs Rust network protocol 2634 and build 167398. Joining requires the same protocol on your game; Steam updates it for you.

Where can you find TESTTTTT?

A region is not published by TESTTTTT. The location shown by Rust Player Count is the one a server provides; it does not verify where the machine actually is. You can reach it at 5.182.207.231:11000.

Is TESTTTTT lag-free?

In the last 48 hours, it averaged 312 server fps, with a low of 251. Up to 419,152 entities were present, including buildings, deployables and other world objects. Peak memory use was 7,643 MB. Lag, as players experience it, is caused by low fps and increasing entities.

Wipe days

What should you expect on TESTTTTT during a wipe?

The average busiest point in recent wipes reached 1 players. The latest wipe saw its biggest crowd 0 hours in. Half that peak was maintained until the next wipe in 50% of recent wipes. If not, the crowd went below half by day 1.

What wipe pattern does TESTTTTT follow?

With too few of TESTTTTT's wipes on record to verify the schedule, the tag guides the prediction. A wipe is scheduled for Saturday 24 October at 19:22 UTC. It has been running its current world for 12 days 22 hours. Its tags list a wipe schedule of every two weeks.

How to join

How can I connect to TESTTTTT?

Joining is done by opening the console (F1) and running client.connect 5.182.207.231:11000. Another way is the Launch Rust option on this page, which uses Steam to start Rust and put you in. You can find its website at https://rust-z.gamestores.app/.

Server tags

what each one means

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

Game

gmrust
Game mode The usual Rust survival experience.
mp0
Max players 0 slots are available.
ts8
Group limit This uses the default team cap: 8 players.
v2634
Protocol Your game version needs to be on protocol 2634 to connect.
cs167398
Build It runs on game build 167398.
ptrak
Networking It uses RakNet, the game's default networking.
$r?
Region code The region code field is empty.

Wipe schedule

^b
Biweekly The server wipes on a two-week cycle.

Difficulty

^h
Hardcore Hardcore mode from Facepunch: survival is harder and help is scarcer.

Gameplay

^p
PvE No player-versus-player combat: the environment provides the danger.

Mods and access

^o
Oxide The plugin framework Oxide (uMod) is in use.
^z
Modded It appears under Modded because plugins or settings modify the game.

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.