Rust Server IndexCard catalogue of Rust servers

Holdings11,632 servers38,138 players105 fresh wipes

Call no.11819 On the shelf · online

TESTSERVER

Online 141.95.13.69:26111 checked 9m ago

Subjects 1. modded2. carbon
Players now
0/ 50
0% full
7-day average
0
peak 1
Rank
#11,819
top 53%
Last wipeWiped8 OCT2026 · 19d 12h ago
19d ago · no schedule published
Next wipe
–
too few wipes seen yet
Call slipPaste it into the F1 console
Record sheet A · appended

Players

AveragePeak
00.250.50.75107:0016:0001:0011:0020:0005:00

Hourly average and peak, UTC.

Record sheet B · appended

Server performance

05010015020007:0016:0001:0011: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.

Record sheet C · appended

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

Record sheet D · loan terms

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.

usual gap
7 daysbetween real wipes
wipe-day peak
0players, last three wipes

The first 48 hours of its last wipes

Thu 8 OctThu 1 Oct
01234+0h+9h+19h+28h+38h+47h

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

Record sheet E · date due

Wipes

newest first
WipedPeakCrowdLastedPlayers before
8 OCT 2026Thu 8 Oct, 18:07 UTC19d ago
0 – running 0
1 OCT 2026Thu 1 Oct, 18:07 UTC FW26d ago
0 – 7 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.

Shelf list · shelved beside it

Similar servers

The same kind of game, then region, group limit, rate and wipes.

ShockRust | Blue | NoLimitno group limit · 156 on average
97/ 500
EU
МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average
125/ 100
EU
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 115 on average
99/ 225
EU
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 88 on average
41/ 700
EU
RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average
5/ 200
EU
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average
16/ 1000
Reference desk

Quick answers

From the figures on this page.

Settings and map

On TESTSERVER, which rules and settings apply?

The name of TESTSERVER does not state a gather rate. 8 players per group is the default limit. Filed under survival, gather, build and raid: the standard game. Fighting and raiding other players is permitted. Plugins or settings change the game; it is listed under Modded in the server browser. Filed under plugins: Carbon. VAC is on: Valve's anti-cheat is enabled.

Which map is in use on TESTSERVER?

Size 4,500, seed 246426222: the game generates the procedural map on TESTSERVER. From this page you can view the map on RustMaps; the same size and seed give the same map.

Lists and filters

On Rust Server Index, which lists and filters carry TESTSERVER?

These lists on Rust Server Index take TESTSERVER: Modded Rust servers, filed by play style. Filed under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Which tags are attached to TESTSERVER, and what do they stand for?

These are the tags TESTSERVER publishes; the game's server browser reads this list: gmrust (Game mode): Rust survival, as standard; mp50 (Max players): The queue ceiling sits at 50; ts8 (Group limit): The team limit is 8, as in the standard game; v2635 (Protocol): Your client must run protocol 2635 to connect; cs168909 (Build): It runs build 168909; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): A region code is absent; ^z (Modded): Modded: the game is changed by plugins or settings; ^y (Carbon): Carbon provides the plugin framework. The top of this page shows three items from the tags: players at present, queue and world creation time.

Wipe schedule

What happens on wipe day at TESTSERVER?

The average peak across its recent wipes is 0 players. 0 hours into the latest wipe, the crowd reached its peak.

How often is TESTSERVER wiped, and on what schedule?

TESTSERVER's rhythm cannot be told yet: too few of its wipes are on record. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. Its present world dates from 19 days 12 hours.

Population

Where does TESTSERVER sit in the rankings?

The seven-day player-hours ranking places TESTSERVER at #11,819, among the top 53% of ranked servers.

How many players are on TESTSERVER at the moment?

TESTSERVER is currently showing 0 players on 50 slots. Filed under seven-day figures: an average of 0 players and a peak of 1. Filed under busiest hour: 04:00 UTC in the last 48 hours, averaging 1 players.

Server facts

What version does TESTSERVER use?

Rust network protocol 2635 and build 168909 on Linux is what you will find on TESTSERVER. Steam keeps your game updated, but the protocol must match for you to join.

What is the uptime and current status of TESTSERVER?

You will find TESTSERVER online as of now. Its reported uptime gives the last restart as roughly 43 hours ago. It was up 168 of 168 hours across the last 7 full days, or 100% of the time. The earliest sighting at Rust Server Index is 13 September 2026.

Is the performance on TESTSERVER good?

Averaged over the last 48 hours, server fps was 94, with a low of 57. Buildings, deployables and everything else in the world came to as many as 122,652 entities. Up to 6,381 MB of memory was in use. A climbing entity count and low fps are felt by players as lag.

Which region is TESTSERVER in?

TESTSERVER gives no region at all. No lookup of the machine's position is made by Rust Server Index; it shows where the server says it is. Connection details: 141.95.13.69:26111.

Joining the server

How can you connect to TESTSERVER?

Two ways in. Type client.connect 141.95.13.69:26111 into the Rust console after pressing F1, or use Launch Rust and join on this page, which opens Rust through Steam and connects you.

Subject headings explained

Server tags

What each one means.

Published as mp50,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y

Game

gmrust
Game mode Rust survival, as standard.
mp50
Max players The queue ceiling sits at 50.
ts8
Group limit The team limit is 8, as in the standard game.
v2635
Protocol Your client must run protocol 2635 to connect.
cs168909
Build It runs build 168909.
ptrak
Networking The standard RakNet layer carries the connection.
$r?
Region code A region code is absent.

Mods and access

^z
Modded Modded: the game is changed by plugins or settings.
^y
Carbon Carbon provides the plugin framework.

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.