RUST METRICSFlight deck · live data
Data live Servers11,772 Players62,070 Populated3,548 Fresh wipes 3 h127 Scan5 min
‹ All servers213.173.13.3:25566
Online Full Queue Fresh wipe Wipe due No query

carbon test 3

Online 213.173.13.3:25566 checked 7m ago

moddedoxide
COM 1 · connect

Server instruments

last reading Wed 20:00 UTC
0 10 20 30 40 PAX 0 /40

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS 152 SERVER FPS

Server fps

48 h low 60 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 46,751 ×1000

Entities

48 h range 44,856–47,176 · memory 3,086 MB
1239 ET SINCE RESTART 13D 03H

Uptime

13 days 3 hours since its last restart, at the last reading
7-day average0peak –
Rank#15,339top 69%
Last wipe13d agono schedule published
Next wipe–too few wipes seen yet
Memory3,086MBat the last reading
REC 1

Players

AveragePeak
0123423:0008:0017:0001:0010:0020:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020023:0008:0017:0001:0010:0020: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 21 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
15k10k15k20k21 Sep28 Sep6 Oct13 Oct21 Oct28 Oct

Top 69% 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.

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 15 Oct, 16:54 UTC13d ago 1 – running 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 carbon test 3 when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 18 hours in.

What wipe timing does carbon test 3 follow?

The rhythm of carbon test 3's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 13 days 5 hours ago.

Lists and filters

Which tags does carbon test 3 carry, and what do they mean?

These are the tags carbon test 3 publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp40 (Max players): The server holds 40 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): Game build reading: 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does carbon test 3 appear in Rust Metrics lists and filters?

Rust Metrics lists featuring carbon test 3: 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; Last wipe: In the last 2 weeks.

Player count

What position does carbon test 3 hold among Rust servers?

Player hours over seven days put carbon test 3 at #15,339, in the top 69% of all ranked servers.

What player count does carbon test 3 carry?

0 of 40 slots are filled on carbon test 3 right now. Seven-day reading: 0 players on average.

Operator and location

Which location does carbon test 3 run from?

No region tag on carbon test 3. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 213.173.13.3:25566.

What Rust version is carbon test 3 on?

Rust network protocol 2634 and build 167781 on Linux is the build carbon test 3 runs. Matching protocol is required to join. Let Steam update your game.

How does carbon test 3 perform?

Check: fps. Average 163 server fps over the last 48 hours, low of 60. Within range. Reading: 47,176 entities at the highest. That covers buildings, deployables and everything else. Memory peak: 3,143 MB. What players call lag comes from low fps and an entity count on the rise.

Is carbon test 3 up, and how often does it stay up?

Check: connection. carbon test 3 is online at this moment. By its reported uptime, the last restart was roughly 13 days 3 hours ago. Reading: 100% uptime over the last 7 full days. It was up 168 of 168 hours. The first sighting on Rust Metrics was 21 September 2026.

Rules and settings

What settings and rules apply on carbon test 3?

Check: gather rate. The name carbon test 3 does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Oxide of them. Anti-cheat reading: VAC on, Valve's system.

Which map is live on carbon test 3?

Check: map. Procedural, size 3,000, seed 7824527, generated by the game on carbon test 3. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Connection

What do you do to join carbon test 3?

Press F1 in Rust and enter client.connect 213.173.13.3:25566. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. You can find its website at https://peachyservers.com.

PLACARDS

Server tags

what each one means

Published as mp40,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp40
Max players The server holds 40 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167781
Build Game build reading: 167781.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Check: category. Modded, because plugins or settings alter 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.