RS-14212Community server
test_server
Offline 46.63.106.19:28015 checked 12d ago
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 60% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
| 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.
Similar servers
The same kind of game, then region, group limit, rate and wipes.
Quick answers
From the figures on this page.
Player activity
What is the typical player count on test_server?
Currently, test_server is offline; the last sighting was 12 days 18 hours ago.
How is test_server ranked?
The last seven days of player hours place test_server at #14,212, in the top 60% of ranked servers.
Tags, lists, and filters
On Top Rust Servers, which lists and filters carry test_server?
These Top Rust Servers lists include test_server: Best Rust community servers. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the tags on test_server?
Published by test_server for the game's server browser to read: gmrust (Game mode): Survival follows the standard Rust ruleset; mp10 (Max players): Player slots: 10; ts8 (Group limit): 8 per team is the default limit; v2634 (Protocol): This server runs protocol 2634; match it to connect; cs166465 (Build): Game build: 166465; ptrak (Networking): This uses RakNet, Rust's default network layer; $r? (Region code): No region code is assigned. Shown at the top of this page, and also in the tags: its players now, its queue, and the time its world was made.
Settings and map
What map is used on test_server?
test_server uses a procedural map, which the game generates.
What does test_server run for rules and settings?
No gather rate is given in the name test_server. The group limit is the game's default of 8 players. You play survival, standard survival: gathering, building and raiding. You can fight and raid other players. A community server, it is found under the Community tab. The server runs with VAC on.
Server details
What version is test_server running?
On Windows, test_server operates Rust network protocol 2634 and build 166465. Joining requires matching protocols, and Steam updates your game automatically.
What is the server location for test_server?
There is no region published by test_server. Top Rust Servers does not look up where the machine stands; it shows where a server says it is. 46.63.106.19:28015 is its address.
What is the uptime of test_server?
test_server is offline now; the last time it was seen was 12 days 18 hours ago. Across the last 7 full days, it was online for 0 of 168 hours, or 0%. It was first observed by Top Rust Servers on 1 October 2026.
Wipe details
When does test_server wipe?
The record holds too few wipes to determine test_server's pattern. A force wipe happens monthly across all Rust servers; the next is scheduled for Thursday 5 November at 19:00 UTC. The world it is running now dates from 12 days 20 hours ago.
Joining the server
What are the steps to join test_server?
Use the console: open Rust, press F1, and type client.connect 46.63.106.19:28015. Or simply click Launch Rust here; it opens the game through Steam and connects you.