TESTSERVER
141.95.13.69:26111 checked 13m ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 7 days between real wipes
- wipe-day peak
- 0 players, last three wipes
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.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 8 Oct, 18:07 UTC 5d ago | 0 | – | running | 0 |
| Thu 1 Oct, 18:07 UTCFW 12d 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.
Similar servers
Quick answers
Player Numbers
What is the rank of TESTSERVER?
Over the last seven days, TESTSERVER ranks #15,955 in player hours, which is in the top 72% of ranked servers.
Is TESTSERVER busy?
TESTSERVER: 0 players now, with 50 slots available. The seven-day average player count stands at 0.
Tags and Filters
How should the tags on TESTSERVER be interpreted?
Read by the game's server browser, the tags TESTSERVER publishes are: gmrust (Game mode): Rust survival, standard; mp50 (Max players): Slot count is 50; ts8 (Group limit): Teams are limited to 8, the default; v2634 (Protocol): Protocol 2634: join only if your game matches this version; cs167231 (Build): Running build 167231; ptrak (Networking): RakNet is the network layer in use; $r? (Region code): Region code not set; ^z (Modded): Under Modded, because plugins or settings modify play; ^y (Carbon): Uses Carbon for plugins. The top of this page also shows its current players, its queue and the time its world was made, all from the tags.
Where does TESTSERVER appear in BestRustServers.xyz lists and filters?
These BestRustServers.xyz lists include TESTSERVER: Best modded Rust servers. These filters on the server list display it: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
Server Details
TESTSERVER Rust version: which one?
The combination is Rust network protocol 2634 and build 167231 on Linux for TESTSERVER. Joining requires the same protocol; Steam updates your game for you.
TESTSERVER performance: is it smooth?
For the past 48 hours, server fps averaged 120, never dropping below 91. The entity count reached 119,265, covering buildings, deployables and all other world objects. At its highest, memory usage was 6,104 MB. What players experience as lag is low fps combined with a rising entity count.
What is the uptime and reliability of TESTSERVER?
TESTSERVER is currently online. The uptime it reports shows a restart roughly 5 days 16 hours ago. It was up 100% of the time over the last 7 full days, 168 of 168 hours. It was first seen by BestRustServers.xyz on 13 September 2026.
TESTSERVER location: where is it?
No region is given by TESTSERVER. BestRustServers.xyz does not look up where the machine stands; it shows where a server says it is. You can reach it at 141.95.13.69:26111.
Rules and Settings
Which map is used on TESTSERVER?
On TESTSERVER, the map is procedural, size 4,500 with seed 246426222, generated by the game. The map can be viewed on RustMaps from this page, since size and seed fix it.
What are the settings and rules for TESTSERVER?
The name TESTSERVER carries no gather multiplier. No group limit is stated; the game's default of 8 players applies. It runs survival, gather, build, raid: the standard game. Fighting and raiding between players are allowed. The Modded section of the browser holds it: plugins or settings apply. Plugin count: Carbon. The server has VAC on.
Wipe Information
When does TESTSERVER wipe?
Too few wipes are on record for TESTSERVER to reveal its rhythm. A force wipe, next on Thursday 5 November at 19:00 UTC, takes every Rust server with it. The world in play was made 5 days 18 hours.
On TESTSERVER, what occurs on wipe day?
Across its recent wipes, the busiest point averaged 0 players. 0 hours into the latest wipe, the crowd reached its peak.
How to Join
How can I connect to TESTSERVER?
Enter client.connect 141.95.13.69:26111 in the console (F1 in Rust), or use Launch Rust on this page to open Steam and connect.
Server tags
Published as mp50,ptrak,$r?,v2634,gmrust,cs167231,ts8,^z,^y
Game
gmrust- Game mode Rust survival, standard.
mp50- Max players Slot count is 50.
ts8- Group limit Teams are limited to 8, the default.
v2634- Protocol Protocol 2634: join only if your game matches this version.
cs167231- Build Running build 167231.
ptrak- Networking RakNet is the network layer in use.
$r?- Region code Region code not set.
Mods and access
^z- Modded Under Modded, because plugins or settings modify play.
^y- Carbon Uses Carbon for plugins.
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.