test_server
Offline 46.63.106.19:28015 checked 26d 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 60% of all ranked servers. Ranked on player hours over the last seven days.
Bx1Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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 day
What is the wipe schedule on test_server?
test_server has too few wipes on record yet for its rhythm to show. Thursday 5 November at 19:00 UTC is the next monthly force wipe, when every Rust server wipes. The world it runs now dates from 26 days 20 hours ago.
Population
How busy is test_server?
Last seen 26 days 18 hours ago, test_server is offline at the moment.
How does test_server rank against other Rust servers?
The top 60% of ranked servers includes test_server, at #14,212 for player hours over the last seven days.
Settings and rules
Which map does test_server run?
test_server runs a procedural map, which the game generates.
What are the rules and settings on test_server?
A gather rate is not given in the name test_server. 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. In the server browser it appears under Community, as a community server. The server has VAC, Valve's anti-cheat, turned on.
Server details
Which version of Rust does test_server run?
Rust network protocol 2634 and build 166465 is the build test_server runs, on Windows. Steam updates your game for you, and the protocol has to match for you to join.
Is test_server online, and how reliable is it?
test_server is down just now; the last sighting was 26 days 18 hours ago. 0 of 168 hours up over the last 7 full days, which is 0%. The first record of it on Rust Heatmap is 1 October 2026.
Where is test_server located?
Nothing about a region comes from test_server. Rust Heatmap shows the location a server states. It does not look up the machine's location. You can reach it at 46.63.106.19:28015.
Tags
Which Rust Heatmap lists and filters include test_server?
The Rust Heatmap lists that test_server fits are: Best Rust community servers. These are the filters that return it on the list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
What do the server tags on test_server mean?
These are the tags test_server publishes for the game's server browser to read: gmrust (Game mode): Survival in the standard Rust form; mp10 (Max players): The slot count is 10; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): The server runs game protocol 2634, so your game has to match it; cs166465 (Build): This build is 166465; ptrak (Networking): Standard game networking here, which is RakNet; $r? (Region code): No region code is set. The top of this page also shows the tags for players now, the queue and when the world was made.
How to join
How do I join test_server?
Enter client.connect 46.63.106.19:28015 in the console, opened with F1 in Rust. Or use Launch Rust here, which opens the game through Steam and connects you.