TESTSERVER
Online 141.95.13.69:26111 checked 9m ago
Server instruments
last reading Tue 23:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 57 · below 20 is lag, below 10 is badEntities
48 h range 98,881–122,652 · memory 6,225 MBUptime
1 days 13 hours since its last restart, at the last readingPlayers
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.
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 | 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 32/500
- 120/100
- 58/225
- 53/700
- 12/200
- 14/1000
Quick answers
from the figures on this pageReset cycle
What should you expect from wipe day on TESTSERVER?
The busiest point of its recent wipes drew 0 players on average. After the latest wipe, numbers topped out at 0 hours.
When does TESTSERVER wipe?
Its rhythm cannot be told from the wipes of TESTSERVER on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 19 days 6 hours ago the current world was made.
Lists and filters
How should you read the tags on TESTSERVER?
Tags published by TESTSERVER, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): 50 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Check: framework. Carbon. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show TESTSERVER?
These Rust Metrics lists carry TESTSERVER: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Population
Where does TESTSERVER sit in the rankings?
Ranking for TESTSERVER: #11,783 on seven-day player hours, top 53% of all ranked servers.
How full does TESTSERVER get?
Current headcount on TESTSERVER: 0 players, 50 slots available. Check: players over seven days. Average 0, peak 1. The last 48 hours peaked at 04:00 UTC, averaging 1 players at that hour.
Server
Which location does TESTSERVER run from?
No region comes from TESTSERVER. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 141.95.13.69:26111.
What Rust version is TESTSERVER on?
Reading: TESTSERVER, Rust network protocol 2635 and build 168909, Linux. Check: protocol. To join, your game must match; Steam handles the update.
Is performance on TESTSERVER within range?
Check: fps. Average 98 server fps over the last 48 hours, low of 57. Within range. Peak entity count: 122,652. Buildings, deployables and all else included. Memory peak: 6,225 MB. Expect lag when fps falls and entities climb.
Is TESTSERVER up, and how often does it stay up?
Reading: online. TESTSERVER answers right now. Reading: uptime. About 37 hours ago it restarted, on its own count. Reading: 86% uptime over the last 7 full days. It was up 144 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.
Map and rules
What settings and rules apply on TESTSERVER?
No gather rate appears in the name: TESTSERVER. 8 players per group, the default value. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Plugin count: Carbon. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on TESTSERVER?
From seed 246426222, the game generates the procedural map on TESTSERVER. Its size is 4,500. View it on RustMaps from this page: matching size and seed give an identical map.
Connection
What do you do to join TESTSERVER?
To join: start Rust, press F1 and type client.connect 141.95.13.69:26111. Or press Launch Rust here and Steam opens the game and connects you.