TESTSERVER
Online 141.95.13.69:26111 checked 10m ago
Measurements
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 53% 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.
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 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.
Quick answers
Population
How does TESTSERVER rank against other Rust servers?
Over the past week it ranks #11,814 for player hours, which puts TESTSERVER in the top 53% of all ranked servers.
How busy is TESTSERVER?
The count reads 0 players on TESTSERVER, which has 50 slots. We counted an average of 0 players in the past week, with 1 at the busiest. In the last 48 hours the peak hour came at 04:00 UTC, averaging 1 players.
Lists and tags
What do the server tags on TESTSERVER mean?
The game's server browser reads the tags TESTSERVER publishes: gmrust (Game mode): The game mode is standard Rust survival; mp50 (Max players): The server has 50 slots; ts8 (Group limit): 8 per team is the default limit; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): This server runs game build 168909; ptrak (Networking): RakNet is the network layer here, as standard for the game; $r? (Region code): The region code is left blank; ^z (Modded): This server appears under Modded because plugins or settings alter the game; ^y (Carbon): A plugin framework, Carbon, is in use. You will see the player count, queue and world creation time at the top of this page, because the tags carry them too.
Which Rust Population lists and filters include TESTSERVER?
On Rust Population, TESTSERVER is filed under these lists: Modded Rust servers, counted. These are the filters it appears under when you browse the list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Wipe notes
What does wipe day look like on TESTSERVER?
Averaged over recent wipes, 0 players were counted at the busiest point. Peak came 0 hours into the latest wipe.
What is the wipe schedule on TESTSERVER?
Its rhythm cannot be told yet: too few of TESTSERVER's wipes are on record. The next monthly force wipe is on Thursday 5 November at 19:00 UTC; all Rust servers wipe then, this one too. 19 days 15 hours ago the current world was made.
Settings
Which map does TESTSERVER run?
A procedural map of size 4,500 from seed 246426222, generated by the game, is in use on TESTSERVER. Size and seed together fix the map, so you can view it on RustMaps from this page.
What are the rules and settings on TESTSERVER?
The name tells you nothing about gather rates: TESTSERVER states none. Eight players per group is the default, and it applies here. You get survival here, gather, build and raid, as in the standard game. Combat between players, raids included, is permitted. The server browser files it under Modded, where plugins or settings alter the game. You will find Carbon running as plugins. You play with Valve's anti-cheat on: VAC.
Server details
Which version of Rust does TESTSERVER run?
The setup is Rust network protocol 2635 and build 168909 on Linux for TESTSERVER. Your game needs the same protocol to join; Steam takes care of updating it.
Does TESTSERVER run smoothly?
In the last 48 hours, it averaged 92 server fps, with a low of 57. Entities peaked at 122,652, including buildings, deployables and everything else. Up to 6,381 MB of memory was used. Lag, as players feel it, is low fps combined with a climbing entity count.
Is TESTSERVER online, and how reliable is it?
Right now, TESTSERVER is online. The uptime it reports suggests a restart roughly 46 hours ago. It was up 100% of the time over the last 7 full days, 168 out of 168 hours. The first sighting by Rust Population was on 13 September 2026.
Where is TESTSERVER located?
Nothing published by TESTSERVER states a region. The location a server claims is what Rust Population shows, not the place where the machine stands. You will find it at 141.95.13.69:26111.
Getting in
How do I join TESTSERVER?
Either enter client.connect 141.95.13.69:26111 in Rust's console after pressing F1, or use Launch Rust here to open Rust through Steam and be connected.