Local forecast
TESTSERVER
Online 141.95.13.69:26111 checked 10m ago
Current conditions
observed 10m agoplayers now
0% full
- 7-day average
- 0
- peak 1
- Rank
- #11,809
- top 53%
- Last wipe
- 19d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
Next wipe
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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.
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.
Past weather: its wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 8 Oct, 19:07 UKThu 8 Oct, 18:07 UTC · 19d ago | 0 | – | running | 0 |
| Thu 1 Oct, 19:07 UK FWThu 1 Oct, 18:07 UTC · 26d 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. The weather: fair when the crowd held, showers when it halved within two days, a storm for the force wipe.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer facts
Does TESTSERVER hold a steady performance?
Its average over the last 48 hours was 97 server fps, and it never dropped below 57. The world held as many as 122,652 entities, buildings and deployables included. At most it drew 6,381 MB of memory. Lag is what players call it when fps is low and entities are piling up.
Is TESTSERVER online at the moment, and how consistent is its uptime?
Right now TESTSERVER is up and running. Going by its reported uptime, the last restart was about 40 hours ago. It was up for 168 of 168 hours across the last 7 full days, 100% of the time. It came to Rust Wipe Stats's notice first on 13 September 2026.
What location is TESTSERVER based in?
No region is published by TESTSERVER. The location Rust Wipe Stats shows is the one the server claims; the machine's real position is not looked up. You can reach it at 141.95.13.69:26111.
What version of Rust is running on TESTSERVER?
On TESTSERVER you will find Rust network protocol 2635 and build 168909, hosted on Linux. To join you need the same protocol, and Steam handles the update.
Server tags
Which meaning sits behind each tag on TESTSERVER?
The server browser reads these tags from TESTSERVER: gmrust (Game mode): Standard survival, the Rust way; mp50 (Max players): It holds 50 players; ts8 (Group limit): The default cap of 8 per team applies here; v2635 (Protocol): Joining needs game protocol 2635 on your copy of the game; cs168909 (Build): It runs game build 168909; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): No region has been set; ^z (Modded): Plugins or settings alter the game here, so it is listed under Modded; ^y (Carbon): Carbon is the plugin framework it runs. The tags hold the current players, the queue length and the world's creation time, and these appear at the top of this page.
Where does TESTSERVER appear among the Rust Wipe Stats lists and filters?
These Rust Wipe Stats lists include TESTSERVER: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Rules and settings
What map is TESTSERVER on?
A procedural map of size 4,500 with seed 246426222, generated by the game, runs on TESTSERVER. You can look at it on RustMaps from this page: same size and seed, same map.
What settings does TESTSERVER use, and what rules does it enforce?
No gather rate appears in the name TESTSERVER. The default of 8 players is the group limit here. It plays as survival, the usual game of gathering, building and raiding. You can fight other players and raid their bases. The server browser lists it as Modded, where plugins or settings alter the game. It runs these plugin frameworks: Carbon. This server has VAC switched on.
Wipe days
When does TESTSERVER wipe?
The record of TESTSERVER's wipes is too thin yet to show its rhythm. The next monthly force wipe, which every Rust server takes, is on Thursday 5 November at 19:00 UTC. 19 days 9 hours is how long the current world has been running.
What happens on TESTSERVER when wipe day arrives?
The average peak across its recent wipes was 0 players. 0 hours after the latest wipe, the crowd hit its peak.
Player counts
How many players does TESTSERVER hold?
The live count for TESTSERVER: 0 players, with 50 slots in total. The seven-day average is 0 players, with a peak of 1. Its busiest point in the last 48 hours was 04:00 UTC, averaging 1 players.
Where does TESTSERVER sit in the rankings?
The last seven days of player hours rank TESTSERVER at #11,809, in the top 53% of ranked servers.
Getting in
What do you do to join TESTSERVER?
Open the console in Rust with F1, then type client.connect 141.95.13.69:26111 to join. On this page, Launch Rust does the same through Steam.