TestServer
Offline 93.115.23.170:28505 checked 3h ago
Li2Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Li3Server 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. From asking the server directly; low fps and a climbing entity count mean lag.
Li4Rank
daily · 1 is bestTop 20% of all ranked servers. Ranked on player hours over the last seven days.
Bx1Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. 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 1, 0 hours in.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sun 25 Oct, 10:22 UTC4d ago | 1° | – | running | 1 |
| Wed 14 Oct, 19:11 UTC15d ago | 1° | held half | 10.6 days | 1 |
| Fri 9 Oct, 22:11 UTC20d ago | 1° | held half | 4.9 days | 0 |
| Thu 8 Oct, 20:05 UTC21d ago | 1° | – | 1.1 days | 1 |
| Thu 8 Oct, 10:38 UTC21d ago | 1° | – | 0.4 days | 0 |
| Wed 7 Oct, 19:48 UTC22d ago | 1° | – | 0.6 days | 0 |
| Fri 2 Oct, 13:09 UTC27d ago | 1° | halved by day 1 | 5.3 days | 1 |
| Wed 30 Sep, 18:09 UTC29d ago | 1° | – | 1.8 days | 1 |
| Tue 29 Sep, 18:24 UTC30d ago | 1° | – | 1 days | 0 |
| Fri 25 Sep, 12:29 UTC34d ago | 1° | held half | 4.2 days | 1 |
| Tue 22 Sep, 17:02 UTC37d ago | 1° | held half | 2.8 days | 1 |
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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe schedule
What does wipe day look like on TestServer?
The average peak across its recent wipes is 1 players. The crowd on the latest wipe reached its peak 0 hours in. Half the peak was held until the next wipe in 100% of its recent wipes.
What is the wipe schedule on TestServer?
Wipes come at irregular times on TestServer, so no next wipe can be predicted. Next on Thursday 5 November at 19:00 UTC, the monthly force wipe resets every Rust server. 4 days 13 hours ago the server made the world it is on now.
Population
How busy is TestServer?
TestServer went quiet 3 hours ago and is offline right now. A seven-day average of 1 players, with a peak of 1. Its busiest point in the last 48 hours was 19:00 UTC, averaging 1 players.
How does TestServer rank against other Rust servers?
Ranked #4,435 on seven-day player hours, TestServer is in the top 20% of all ranked servers.
Settings and rules
Which map does TestServer run?
The game generates the procedural map on TestServer.
What are the rules and settings on TestServer?
No gather rate appears in the name TestServer. The group limit is 8 players, which is the game's default. survival is the game mode, standard play: gathering, building and raiding. Combat between players and raiding are both possible. Plugins or settings change the game, and it is listed under Modded in the server browser. Plugin count: Carbon. VAC is on, which is Valve's anti-cheat.
Server details
Which version of Rust does TestServer run?
The build on TestServer is Rust network protocol 2635 and build 168909, running on Windows. To join, your game must match the protocol; Steam handles the update.
Is TestServer online, and how reliable is it?
Last seen 3 hours ago, TestServer is offline right now. 54 of 168 hours up over the last 7 full days, which is 32%. The first record of it on Rust Heatmap is 13 September 2026.
Where is TestServer located?
A region is not published for TestServer. What Rust Heatmap shows is where a server says it is. Where the machine stands is not looked up. You can reach it at 93.115.23.170:28505.
Tags
Which Rust Heatmap lists and filters include TestServer?
Modded Rust servers, by live population are the Rust Heatmap lists that TestServer fits. Filtering the list by Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week brings it up.
What do the server tags on TestServer mean?
These are the tags TestServer publishes for the game's server browser to read: gmrust (Game mode): Survival in the standard Rust form; mp50 (Max players): The slot count is 50; ts8 (Group limit): The game default applies: 8 per team at most; v2635 (Protocol): Your game must match protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): Standard game networking here, which is RakNet; $r? (Region code): The region code is blank; ^z (Modded): Settings or plugins alter the game, which puts it under Modded; ^y (Carbon): The plugin framework in use is Carbon. Players now, the queue and the world's creation time sit in the tags as well and appear at the top of this page.
How to join
How do I join TestServer?
To join by console, open it with F1 in Rust and enter client.connect 93.115.23.170:28505. Or press Launch Rust on this page, which connects you through Steam.