Station XX-11831 · recording
TESTSERVER
Online 141.95.13.69:26111 checked 12m ago
- Players now
- 0/ 50
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak 1
- Rank
- #11,831
- top 53%
- Last wipe
- 19d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 50 slots
- Motion · 24 h
- M0.0■steady+0 players
- Sharpest hour
- −1into Tue 05:00 UTC
- Peak · 48 h
- 1most players in any hour
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
daily · 1 is bestTop 53% of all ranked servers. Ranked on player hours over the last seven days.
Wipe 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.
- usual gap
- 7 daysbetween real wipes
- wipe-day peak
- 0players, 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
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 8 Oct, 18:07 UTC19d ago | M0.0■steady | 0 | – | running | 0 | |
| Thu 1 Oct, 18:07 UTC FW26d ago | M0.0■steady | 0 | – | 7 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageRules and settings
Which map is running on TESTSERVER?
Generated by the game, the map on TESTSERVER is procedural, size 4,500 with seed 246426222. From this page you can look at it on RustMaps, since the same size and seed give the same map.
Which settings and rules apply on TESTSERVER?
No gather rate appears in the name of TESTSERVER. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Carbon. VAC, Valve's anti-cheat, is switched on.
Live population
What is the current population on TESTSERVER?
At this moment, TESTSERVER records 0 players across 50 slots. The seven-day average is 0 players, with a peak of 1. The last 48 hours show their highest activity at 04:00 UTC, averaging 1 players.
How does TESTSERVER rank against other Rust servers?
Over the last seven days, TESTSERVER recorded enough player hours to reach #11,831 worldwide, placing it in the top 53% of all ranked servers.
Server facts
How reliably does TESTSERVER stay online?
TESTSERVER is up at the moment. Going by the uptime figure it reports, it restarted about 2 days ago. Of the 168 hours in the last 7 full days, it was up for 168, or 100% of the time. On 13 September 2026 it was recorded for the first time by Rust Server Trends.
Does TESTSERVER hold a steady tick rate?
The 48-hour average is 91 server fps; 66 is the lowest observed. At its highest, it carried 122,652 entities: buildings, deployables and the world's other contents. It reached a ceiling of 6,381 MB of memory. What you feel as lag is the combination of low fps and a rising entity count.
Which region does TESTSERVER run from?
Nothing about a region comes from TESTSERVER. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 141.95.13.69:26111 is the address it uses.
Which Rust version is TESTSERVER running?
Rust network protocol 2635 and build 168909 on Linux is what TESTSERVER runs. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe pattern
What does wipe day look like on TESTSERVER?
The recent wipes averaged a busiest count of 0 players. 0 hours after the latest wipe, the crowd peaked.
On what timetable does TESTSERVER run its wipes?
On record so far are too few of TESTSERVER's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The present world dates from 19 days 17 hours.
Server tags
What do the server tags on TESTSERVER mean?
These are the tags TESTSERVER publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp50 (Max players): Slots: 50; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): A plugin framework, Carbon, runs here. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does TESTSERVER appear?
These Rust Server Trends lists include TESTSERVER: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Connecting
How do you connect to TESTSERVER?
Enter client.connect 141.95.13.69:26111 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.