test
Key statistics
the figures behind the quote- Players now
- 0/ 20 0% full
- Change · 24h
- ▪+0 no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #15,258 top 70%
- Rank · 7d ago
- – not ranked a week ago
- Last wipe
- 3d ago no schedule published
- Next wipe
- – too few wipes seen yet
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 0 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 20 Oct 2026 no hostname published
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
daily · 1 is bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yet- usual gap
- 0.8 days between real wipes
- wipe-day peak
- 0 players, last three wipes
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.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Tue 20 Oct, 23:25 UTC3d ago | 0 | – | running | 0 |
| Tue 20 Oct, 03:19 UTC4d ago | 0 | – | 0.8 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | Rustoria.co - EU MainEU · groups of 16+ · weekly · 589 on average | 512/550 | ▼−328−39.0% | |
| 2 | Rusty Moose |EU Main|EU · groups of 12+ · weekly · 462 on average | 618/675 | ▼−62−9.2% | |
| 3 | Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 359 on average | 438/450 | ▲+69+18.6% | |
| 4 | Rustoria.co - EU East LongEU · groups of 12+ · monthly · 292 on average | 462/500 | ▲+43+10.3% | |
| 5 | Rusty Moose |US Biweekly|NA · groups of 12+ · biweekly · 260 on average | 83/200 | ▼−4−4.9% | |
| 6 | Rustafied.com - EU Medium - LargeEU · groups of 16+ · biweekly · 229 on average | 269/375 | ▼−34−11.4% |
Quick answers
from the figures on this pageMap and Rules
What settings and rules are in place on test?
The name of test carries no gather rate. Up to 8 players per group, which is the game's default. It runs survival, gather, build and raid in the standard game. PvP and raiding are enabled. Community is its listing in the server browser. The server has VAC, Valve's anti-cheat, switched on.
Which map is played on test?
test uses a procedural map, which the game generates.
Player Count
What is the rank of test?
For the last seven days, test holds rank #15,258 on player hours, in the top 70% of all ranked servers.
How full is test?
On test, 0 players are in now, out of 20 slots. Average players over the last seven days: 0.
Wipe Frequency
How does test handle wipe day?
The average peak across its recent wipes is 0 players. 0 hours after the latest wipe, the crowd reached its peak.
On what cycle does test wipe?
The record holds too few of test's wipes to establish its rhythm. The monthly force wipe applies to every Rust server. The next one falls on Thursday 5 November at 19:00 UTC. Its world now is 3 days 15 hours old.
Server Overview
What is the server location for test?
For test, no region is published. Rust Analytics reports the location a server claims, not the machine's actual location. 65.32.145.226:28015 is its address.
test is on which Rust version?
The build is Rust network protocol 2634 and build 167781 on Linux, running on test. Joining requires the same protocol on your game, which Steam updates.
What is the uptime and reliability of test?
Online at this moment: test. 3 full days have passed with 96% uptime, 69 of 72 hours. The earliest Rust Analytics saw it was 20 October 2026.
Tags & Filters
How should you interpret the tags on test?
These tags are published by test and read by the game's server browser: gmrust (Game mode): Rust's standard survival mode; mp20 (Max players): It holds 20 slots; ts8 (Group limit): 8 per team: the default setting, unchanged; v2634 (Protocol): To join, your game needs protocol 2634; cs167781 (Build): Build 167781; ptrak (Networking): Runs on RakNet, Rust's default network layer; $r? (Region code): No region code has been set. The top of this page and the tags both show its players now, its queue and when its world was made.
test appears in which of the lists and filters on Rust Analytics?
These Rust Analytics lists include test: 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 week.
Connection
What is the process to join test?
The console route: start Rust, press F1, enter client.connect 65.32.145.226:28015. The page's Launch Rust button opens Rust through Steam and connects you instead.
Server tags
what each one meansPublished as mp20,ptrak,$r?,v2634,gmrust,cs167781,ts8
Game
gmrust
mp20
ts8
v2634
cs167781
ptrak
$r?
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.