Rust StatisticsWorking papers on every public Rust server · 79,295 players now

carbon test 3

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 12m ago · 213.173.13.3:25566

Abstract

We describe the public Rust server carbon test 3, reached at 213.173.13.3:25566. At the last check it held 0 of 40 places, against a seven-day mean of 01. It ranks #15,323 of all servers, the top 69%. It last wiped 13d ago.

Keywordsmodded oxide

Access. Launch Rust and join Website ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/400% full
In the queue0no queue
Seven-day mean0peak –
Rank2#15,323top 69%
Last wipe13d agono schedule published
Next wipe3–too few wipes seen yet

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

AveragePeak
0123421:0006:0015:0000:0009:0019:00
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
05010015020021:0006:0015:0000:0009:0019:00
Figure 2: Server performance. 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.

4Rank

The server stands in the top 69% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k21 Sep28 Sep6 Oct13 Oct21 Oct28 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: 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.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Wipe-day peak1players, last three wipes
01234+0h+9h+19h+28h+38h+47h
Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 1, 18 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Thu 15 Oct, 16:5413d 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Map of carbon test 3
Figure 5: The map: Procedural Map, size 3000, seed 7824527. Open on RustMaps.
Table 4: The server's published settings.
Address213.173.13.3:25566
Region–
Max players40
Group limit8, the default
Wipe schedule–
Last wipe15 Oct 2026, 16:54 UTC
Hostname–
First seen21 Sep 2026
MapProcedural Map
Size3000
Seed7824527

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are browse modded Rust servers [2] and next Rust wipe times [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
ShockRust | Blue | NoLimitno group limit · 157 on average141/500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 127 on average125/100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 115 on average150/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 90 on average114/700
RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average35/200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average33/1000

Appendix AQuick answers

From the figures on this page.

About the server

A.1Is the performance of carbon test 3 smooth?

Over the past 48 hours, it ran at an average of 163 server fps, with a low of 60. Buildings, deployables and all other world objects counted together reached a maximum of 47,176 entities. The peak memory usage was 3,143 MB. When fps is low and entity count climbs, players feel lag.

A.2What location does carbon test 3 have?

No region is published by carbon test 3. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. 213.173.13.3:25566 is its address.

A.3What is the online status and reliability of carbon test 3?

carbon test 3 is currently online. The uptime it reports indicates a restart about 12 days 23 hours ago. The server was up 100% of the time over the last 7 full days, 168 of 168 hours. Its first appearance in Rust Statistics's records is 21 September 2026.

A.4What is the Rust version for carbon test 3?

carbon test 3 is running Rust network protocol 2634 and build 167781 on the Linux operating system. Steam updates your game for you, but you must be on the same protocol to join.

Wipe timing

A.5When are wipes carried out on carbon test 3?

The record of carbon test 3's wipes is not yet sufficient to establish its rhythm. Wiping is compulsory for every Rust server at the monthly force wipe, the next of which is Thursday 5 November at 19:00 UTC. The current world has been running for 13 days 3 hours.

A.6How would you describe wipe day on carbon test 3?

Across its recent wipes, the average peak population was 1 players. The crowd reached its maximum 18 hours after the latest wipe.

Player count

A.7How does carbon test 3 compare with other Rust servers in the rankings?

The seven-day player-hours ranking puts carbon test 3 at #15,323, within the top 69% of ranked servers.

A.8What is the population level of carbon test 3?

On carbon test 3, 0 of the 40 slots are occupied at present. Averaged across the last seven days, the population is 0 players.

Tags and filters

A.9How should the tags on carbon test 3 be interpreted?

The game's server browser reads gmrust (Game mode): Survival on standard Rust rules; mp40 (Max players): It offers 40 slots; ts8 (Group limit): Teams are limited to 8, as the game defaults; v2634 (Protocol): Your game must run protocol 2634 to connect; cs167781 (Build): Build 167781 is the one running; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): The region code is unset; ^o (Oxide): Plugins are handled by Oxide (uMod); ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded, which carbon test 3 publishes as its tags. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.10Where can carbon test 3 be found among the Rust Statistics lists and filters?

The Rust Statistics lists that carbon test 3 fits are: Modded Rust servers. You will find it on the server list filtered by: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Rules, settings, map

A.11Under what rules and settings does carbon test 3 operate?

No gather rate appears in the name of carbon test 3. No cap is given beyond the game's default of 8 players per group. survival is the game mode here; gather, build and raid: the standard game. Players may raid and fight one another. Plugins or settings change the game; the browser files it under Modded. Oxide plugins are running. The server has VAC on, Valve's anti-cheat.

A.12What is the map for carbon test 3?

Size 3,000 and seed 7824527 define the procedural, game-generated map on carbon test 3. Size and seed being equal, the map is the same, so it can be viewed on RustMaps from this page.

How to join

A.13What is the process for joining carbon test 3?

Press F1 inside Rust to open the console and enter client.connect 213.173.13.3:25566. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection. Its website can be found at https://peachyservers.com.

Appendix BServer tags

What each of the server's tags means. Published as mp40,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp40Max players. It offers 40 slots.
ts8Group limit. Teams are limited to 8, as the game defaults.
v2634Protocol. Your game must run protocol 2634 to connect.
cs167781Build. Build 167781 is the one running.
ptrakNetworking. Networking runs on RakNet, the game's standard layer.
$r?Region code. The region code is unset.
Mods and access
^oOxide. Plugins are handled by Oxide (uMod).
^zModded. The game is altered by plugins or settings, so it is listed as Modded.

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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Browse modded Rust servers. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Next Rust wipe times. ruststatistics.org/rust-servers-wiping-today-list.