TESTSERVER
Online 141.95.13.69:26111 checked 14m ago
Li2Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Li3Server 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.
Li4Rank
daily · 1 is bestTop 53% of all ranked servers. Ranked on player hours over the last seven days.
Bx1Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 8 Oct, 18:07 UTC19d ago | 0° | – | running | 0 |
| Thu 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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe schedule
What does wipe day look like on TESTSERVER?
The average peak across its recent wipes is 0 players. 0 hours after the latest wipe, the crowd peaked.
What is the wipe schedule on TESTSERVER?
The record of TESTSERVER's wipes is not yet long enough to show a rhythm. Next on Thursday 5 November at 19:00 UTC, the monthly force wipe resets every Rust server. The world it runs now dates from 19 days 16 hours ago.
Population
How busy is TESTSERVER?
The current population of TESTSERVER is 0, against 50 slots. The average across the last seven days is 0 players; the peak reached 1. Look at 04:00 UTC for the last 48 hours: that hour averaged 1 players.
How does TESTSERVER rank against other Rust servers?
The top 53% of ranked servers includes TESTSERVER, at #11,821 for player hours over the last seven days.
Rules and settings
Which map does TESTSERVER run?
A procedural map of size 4,500 with seed 246426222, generated by the game, runs on TESTSERVER. The map is the same for a given size and seed, so RustMaps can show it from this page.
What are the rules and settings on TESTSERVER?
No gather rate appears in the name TESTSERVER. 8 players is the default group size, and that is the limit here. The server runs survival, gather, build and raid in the standard game. Players can fight each other, and raids are allowed. In the server browser it is Modded, meaning plugins or settings modify the game. Carbon plugins run on this server. VAC is on, which is Valve's anti-cheat.
About the server
Which version of Rust does TESTSERVER run?
Rust network protocol 2635 and build 168909 on Linux is what TESTSERVER runs. Your game must run the same protocol to join, and Steam takes care of updating it.
Is TESTSERVER online, and how reliable is it?
The server is up at the moment: TESTSERVER is online. About 47 hours ago is when it last restarted, by its own uptime figure. 168 of 168 hours up over the last 7 full days, which is 100%. The first record of it on Rust Heatmap is 13 September 2026.
Where is TESTSERVER located?
No region is published by TESTSERVER. A server says where it is, and Rust Heatmap shows that. The machine's actual location is not looked up. 141.95.13.69:26111 is its address.
Does TESTSERVER run smoothly?
Average server fps over the last 48 hours was 93; it never dropped below 67. The world held as many as 122,652 entities, buildings and deployables included. Memory use reached 6,381 MB at most. Players feel lag when fps falls and the entity count climbs.
Lists and filters
Which Rust Heatmap lists and filters include TESTSERVER?
These Rust Heatmap lists include TESTSERVER: Modded Rust servers, by live population. These are the filters that return it on the list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
What do the server tags on TESTSERVER mean?
These are the tags TESTSERVER publishes for the game's server browser to read: gmrust (Game mode): Survival in the standard Rust form; mp50 (Max players): Slot count: 50; ts8 (Group limit): The game default applies: 8 per team at most; v2635 (Protocol): To join, run the same version: game protocol 2635; cs168909 (Build): The game build here is 168909; ptrak (Networking): Standard game networking here, which is RakNet; $r? (Region code): A region code is not set; ^z (Modded): Settings or plugins alter the game, which puts it under Modded; ^y (Carbon): Plugins run through Carbon. The top of this page also shows the tags for players now, the queue and when the world was made.
How to join
How do I join TESTSERVER?
To join by console, open it with F1 in Rust and enter client.connect 141.95.13.69:26111. Or press Launch Rust on this page, which connects you through Steam.