Server profile
TestServer
Online, with 1 of 50 players on; ranked #4,587 of every public Rust server, the top 21%. It last wiped 4d ago.
Online 93.115.23.170:28505 checked 11m 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. 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 21% of all ranked servers. Ranked on player hours over the last seven days.
The wipe cycle
Wipe schedule
No rhythm it keeps.
Its 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 wipesPlayers each hour, from the hour of the wipe
Note: players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
The record
Wipes
Every wipe we saw, newest first.
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sun 25 Oct, 10:22 UTC4d ago | 1 | – | running | 1 |
| Wed 14 Oct, 19:11 UTC14d ago | 1 | held half | 10.6 days | 1 |
| Fri 9 Oct, 22:11 UTC19d ago | 1 | held half | 4.9 days | 0 |
| Thu 8 Oct, 20:05 UTC20d ago | 1 | – | 1.1 days | 1 |
| Thu 8 Oct, 10:38 UTC21d ago | 1 | – | 0.4 days | 0 |
| Wed 7 Oct, 19:48 UTC21d 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 UTC28d ago | 1 | – | 1.8 days | 1 |
| Tue 29 Sep, 18:24 UTC29d ago | 1 | – | 1 days | 0 |
| Fri 25 Sep, 12:29 UTC34d ago | 1 | held half | 4.2 days | 1 |
| Tue 22 Sep, 17:02 UTC36d ago | 1 | held half | 2.8 days | 1 |
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 cycle
What does TestServer look like once wipe day arrives?
At their busiest, its recent wipes drew 1 players on average. 0 hours after the latest wipe, the crowd peaked. Half the peak held until the next wipe in 100% of its recent wipes.
On what schedule does TestServer wipe?
There is no next wipe to predict: TestServer wipes at irregular times. The monthly force wipe comes to all Rust servers next on Thursday 5 November at 19:00 UTC. 4 days 3 hours have passed since its current world was created.
Server
What Rust version is live on TestServer?
The Rust build is network protocol 2635 and build 168909, running on Windows, for TestServer. You can only join if your game is on the same protocol; Steam handles that update.
How reliable is TestServer, and is it up at the moment?
TestServer is currently reachable and online. It spent 61 of the last 7 full days' 168 hours up, 36% of the time. On 13 September 2026 is when Rust Insights first saw it.
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. You can reach it at 93.115.23.170:28505.
Server tags
Which meanings sit behind the tags on TestServer?
These tags come from TestServer and are read by the game's server browser: gmrust (Game mode): The game mode is standard Rust survival; mp50 (Max players): The slot count is 50; ts8 (Group limit): This is the game default: 8 per team at most; v2635 (Protocol): To join you need the same version; protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet handles the network layer, as it does by default; $r? (Region code): A region code has not been set; ^z (Modded): Modded is its listing, because plugins or settings change how the game plays; ^y (Carbon): Carbon is the plugin framework in use. The tags also hold the current player count, the queue and when the world was created, all of which appear at the top of this page.
On which Rust Insights lists does TestServer appear?
These Rust Insights lists include TestServer: Modded Rust servers, explained. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
Population history
What does the population of TestServer look like?
At the time of this refresh, TestServer holds 1 players on 50 slots. The seven-day average is 1 players, and the highest point in that week was 1. Its strongest hour in the past 48 was 19: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 #4,587, among the top 21% of all ranked servers.
Settings and rules
What are the settings and rules for TestServer?
The name of TestServer does not state a gather rate. The default of 8 players per group is what applies here. You get survival as the game mode, the standard game: gather, build, raid. Fighting and raiding between players are allowed. The server browser lists it under Modded: plugins or settings alter the game. Plugins: Carbon run here. VAC is on: Valve's anti-cheat is active.
Which map is live on TestServer?
A procedural map, generated by the game, is what TestServer runs.
Join
What is the way to join TestServer?
To connect, start Rust and enter client.connect 93.115.23.170:28505 in the console (F1). Or join through Launch Rust on this page, which opens Rust via Steam and connects you.