Server profile
TESTSERVER
Online, with 0 of 50 players on; ranked #11,755 of every public Rust server, the top 53%. It last wiped 18d ago.
Online 141.95.13.69:26111 checked 10m ago
The crowd
Players
Who is on it, hour by hour and day by day.
Source: every five minutes, from the Steam server list.
Note: hourly average and peak, UTC.
Note: daily average and peak, UTC.
Under the hood
Server performance
Frames per second, entities and memory, asked of the server itself.
Note: 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.
The standings
Rank
Its place among every ranked server, day by day; 1 is best.
Note: Top 53% of all ranked servers. Ranked on player hours over the last seven days.
The wipe cycle
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.
The first 48 hours of its last wipesPlayers each hour, from the hour of the wipe
Note: players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
The record
Wipes
Every wipe we saw, newest first.
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 8 Oct, 18:07 UTC18d ago | 0 | – | running | 0 |
| Thu 1 Oct, 18:07 UTC FW25d ago | 0 | – | 7 days | 0 |
Note: 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.
If you like this one
Similar servers
The same kind of game, then region, group limit, rate and wipes.
The short version
Quick answers
From the figures on this page.
Wipe schedule
What should you expect on wipe day at TESTSERVER?
Recent wipes peaked at 0 players on average. 0 hours after the latest wipe, the crowd peaked.
When does TESTSERVER wipe, and how often?
Its rhythm cannot be read yet: TESTSERVER has too few wipes on record. Next on Thursday 5 November at 19:00 UTC, every Rust server, this one included, takes the monthly force wipe. The world you are playing on now was made 18 days 23 hours ago.
Server
What does performance look like on TESTSERVER?
Server fps averaged 102 over 48 hours; the lowest reading was 57. At its highest the entity count reached 122,652: buildings, deployables and everything else. Memory use peaked at 5,908 MB. Lag, for players, is low fps and an entity count that keeps climbing.
Which Rust version is TESTSERVER on?
The Rust build is network protocol 2635 and build 168909, running on Linux, for TESTSERVER. You can only join if your game is on the same protocol; Steam handles that update.
Has TESTSERVER stayed online, and is it up now?
At the time of this check TESTSERVER is online. The uptime it reports puts the last restart at about 30 hours ago. The last 7 full days gave 168 of 168 hours up, or 100% of the time. Rust Insights first logged this server on 13 September 2026.
What location is listed for TESTSERVER?
No region is published by TESTSERVER. Rust Insights takes the location from what a server says about itself; no check is made of where the machine stands. 141.95.13.69:26111 is where it answers.
Server tags
What is meant by each tag on TESTSERVER?
When the game's server browser reads TESTSERVER, it finds these tags: gmrust (Game mode): The game mode is standard Rust survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): 8 to a team, which is the default the game ships with; v2635 (Protocol): To join you need the same version; protocol 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): Rust's standard network layer, RakNet, carries it; $r? (Region code): No region code is set; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): Carbon, a plugin framework, runs on this server. You will find the present player count, the queue and the world's creation time among the tags, and they are displayed at the top of this page.
Which Rust Insights filters and lists feature TESTSERVER?
These Rust Insights lists include TESTSERVER: Modded Rust servers, explained. On the server list, the filters that surface it are Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Population history
How many players are on TESTSERVER right now, and how does that number move?
At the time of this refresh, TESTSERVER holds 0 players on 50 slots. The seven-day average is 0 players, and the highest point in that week was 1. Its strongest hour in the past 48 was 04:00 UTC, with an average of 1 players.
How does TESTSERVER compare with other Rust servers in the ranking?
The player-hours ranking for the last seven days puts TESTSERVER at #11,755, among the top 53% of all ranked servers.
Settings and rules
What are the settings and rules for TESTSERVER?
No gather rate appears in the name of TESTSERVER. The default of 8 players per group is what applies here. You get survival as the game mode, the standard game: gather, build, raid. Players may raid and fight one another. Plugins or settings change the game, so it sits under Modded in the browser. Carbon is the plugin count it runs. VAC is on: Valve's anti-cheat is active.
What is the map on TESTSERVER?
TESTSERVER runs a procedural map of size 4,500 with seed 246426222, generated by the game. You can look at the map on RustMaps from this page, since the same size and seed produce the same map.
How to join
How do you connect to TESTSERVER?
To connect, start Rust and enter client.connect 141.95.13.69:26111 in the console (F1). Or join through Launch Rust on this page, which opens Rust via Steam and connects you.