Rust StatisticsWorking papers on every public Rust server · 85,654 players now

TESTSERVER

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 10m ago · 141.95.13.69:26111

Abstract

We describe the public Rust server TESTSERVER, reached at 141.95.13.69:26111. At the last check it held 0 of 50 places, against a seven-day mean of 0 and a peak of 11. It ranks #11,755 of all servers, the top 53%. It last wiped 19d ago.

Keywordsmodded carbon

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/500% full
In the queue0no queue
Seven-day mean0peak 1, 48 h peak 1
Rank2#11,755top 53%
Last wipe19d 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
00.250.50.75121:0006:0015:0001:0010: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:0001:0010: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 17 Sep.

4Rank

The server stands in the top 53% 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
15k10k15k20k20 Sep27 Sep5 Oct12 Oct20 Oct27 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
Usual gap7 daysbetween real wipes
Wipe-day peak0players, last three wipes
Thu 8 OctThu 1 Oct
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 0, 0 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Thu 8 Oct, 18:0719d ago 0 – running 0
Thu 1 Oct, 18:07fw26d ago 0 – 7 d 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 TESTSERVER
Figure 5: The map: Procedural Map, size 4500, seed 246426222. Open on RustMaps.
Table 4: The server's published settings.
Address141.95.13.69:26111
Region–
Max players50
Group limit8, the default
Wipe schedule–
Last wipe8 Oct 2026, 18:07 UTC
Hostname–
First seen13 Sep 2026
MapProcedural Map
Size4500
Seed246426222

7Similar servers

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

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
ShockRust | Blue | NoLimitno group limit · 163 on average187/500
МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average129/100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 111 on average152/225
RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average31/200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 85 on average152/700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average52/1000

Appendix AQuick answers

From the figures on this page.

Server details

A.1Is the performance of TESTSERVER smooth?

The server fps averaged 100 over the last 48 hours, never dropping below 57. Buildings, deployables and all other world objects counted together reached a maximum of 122,652 entities. Memory use peaked at 5,908 MB. Lag, as players feel it, results from low fps combined with an increasing entity count.

A.2What is the location of TESTSERVER?

No region is published by TESTSERVER. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. You will find it at 141.95.13.69:26111.

A.3What is the reliability of TESTSERVER, and is it online?

TESTSERVER is online at this time. The uptime it reports indicates a restart about 33 hours ago. Its uptime over the last full days (7 days) was 100%, with 168 of 168 hours online. It was first observed on 13 September 2026 by Rust Statistics.

A.4What is the Rust version for TESTSERVER?

Rust network protocol 2635 and build 168909 is the version that TESTSERVER runs, on Linux. To join, your game must use the same protocol; Steam handles the update for you.

Wipe schedule

A.5When are wipes carried out on TESTSERVER?

The record of TESTSERVER'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 19 days 2 hours.

A.6How would you describe wipe day on TESTSERVER?

Across its recent wipes, the average peak population was 0 players. The peak on the latest wipe came 0 hours after it began.

Population

A.7What position does TESTSERVER occupy in the ranking of Rust servers?

Ranked by player hours across seven days, TESTSERVER holds #11,755, in the top 53% of all ranked servers.

A.8What is the population level of TESTSERVER?

On TESTSERVER, 0 of the 50 slots are occupied at present. Averaged over the last seven days: 0 players; the same period peaks at 1. Averaging 1 players, 04:00 UTC was the busiest hour of the past 48.

Tags, lists

A.9What do the tags associated with TESTSERVER signify?

Tags from TESTSERVER, read by the game's server browser, are gmrust (Game mode): Survival on standard Rust rules; mp50 (Max players): The slot count is 50; ts8 (Group limit): The team cap is 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to connect; cs168909 (Build): Build 168909 is the one running; ptrak (Networking): RakNet is the network layer here, as it is by default in the game; $r? (Region code): No region code is set; ^z (Modded): Modded listing: plugins or settings modify the game; ^y (Carbon): Plugins run through Carbon. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.10Where can TESTSERVER be found among the Rust Statistics lists and filters?

These Rust Statistics lists include TESTSERVER: Modded Rust servers. You will find it on the server list filtered by: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Rules, settings, map

A.11Which settings and rules are in force on TESTSERVER?

Its name carries no gather rate for TESTSERVER. At 8 players, the group limit equals the game's default. Listed as survival, the game mode is gather, build and raid: the standard game. Fighting and raiding between players are both permitted. Plugins or settings change the game; the browser files it under Modded. The plugin count is Carbon. VAC is active: that is Valve's anti-cheat.

A.12On which map does TESTSERVER take place?

The game generates TESTSERVER's procedural map at size 4,500, from seed 246426222. Equal size and seed yield an identical map, which this page offers to view on RustMaps.

Connection

A.13How do you connect to TESTSERVER?

Press F1 inside Rust to open the console and enter client.connect 141.95.13.69:26111. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp50,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp50Max players. The slot count is 50.
ts8Group limit. The team cap is 8, which is the game default.
v2635Protocol. Your game must run protocol 2635 to connect.
cs168909Build. Build 168909 is the one running.
ptrakNetworking. RakNet is the network layer here, as it is by default in the game.
$r?Region code. No region code is set.
Mods and access
^zModded. Modded listing: plugins or settings modify the game.
^yCarbon. Plugins run through Carbon.

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. Modded Rust servers listed live. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Upcoming Rust wipes. ruststatistics.org/rust-servers-wiping-today-list.