typical TESTING
Key statistics
the figures behind the quote- Players now
- 0/ 40 0% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #15,894 top 72%
- Rank · 7d ago
- #15,970 ▲76 places up
- Last wipe
- 8d ago no schedule published
- Next wipe
- – no wipe seen yet
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 0 player hours, last seven days
- Map
- 1000 Procedural Map · seed 1
- First seen
- 8 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, measured since 8 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Wipes
newest first| 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| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | Rustoria.co - EU East LongEU · groups of 12+ · monthly · 397 on average | 213/225 | ▼−120−36.0% | |
| 2 | Rusty Moose |EU Monthly|EU · groups of 12+ · monthly · 333 on average | 122/200 | ▼−74−37.6% | |
| 3 | Rusty Moose |US Monthly|NA · groups of 12+ · monthly · 324 on average | 215/250 | ▲+31+17.1% | |
| 4 | Rustoria.co - EU LongEU · groups of 14+ · monthly · 315 on average | 132/200 | ▼−70−34.7% | |
| 5 | Rustoria.co - EU MainEU · groups of 16+ · weekly · 295 on average | 21/250 | ▼−13−37.8% | |
| 6 | Rustafied.com - EU Long - LargeEU · groups of 16+ · monthly · 270 on average | 135/175 | ▼−51−27.3% |
Quick answers
from the figures on this pageMap and Rules
How is typical TESTING configured in terms of rules and settings?
The name of typical TESTING carries no gather rate. The default group size of 8 players applies here. survival is the mode, gather, build and raid in the standard game. PvP and raiding are enabled. The server browser lists it under Community, as a community server. The server has VAC, Valve's anti-cheat, switched on.
What is the current map on typical TESTING?
The map on typical TESTING is procedural, size 1,000, with seed 1, and generated by the game. The map is reproducible from its size and seed; RustMaps shows it from this page.
Player Count
Where does typical TESTING sit in the rankings?
In the top 72% of all ranked servers, typical TESTING is #15,894 on player hours over the last seven days.
What is the population on typical TESTING?
Right now, typical TESTING is offline; the last sighting was 33 hours ago. Average players over the last seven days: 0.
Wipe Frequency
On what cycle does typical TESTING wipe?
There are too few wipes on record for typical TESTING to reveal its rhythm. At the monthly force wipe, every Rust server wipes. That happens next on Thursday 5 November at 19:00 UTC. Its world now is 8 days old.
Server Overview
What is the server location for typical TESTING?
There is no region published for typical TESTING. Rust Analytics reports the location a server claims, not the machine's actual location. 15.204.83.240:21000 is its address.
How is the performance on typical TESTING?
Server fps over the last 48 hours: 240 on average, 240 at the lowest. 4,319 entities is the maximum carried: buildings, deployables and everything else. Up to 816 MB of memory was used. Low fps and growing entities are the source of felt lag.
What Rust version is typical TESTING running?
Rust network protocol 2634 and build 167398 on Linux is what typical TESTING runs. Joining requires the same protocol on your game, which Steam updates.
What is the uptime and reliability of typical TESTING?
Offline at this moment: typical TESTING. Last seen 33 hours ago. Its own uptime figure dates the last restart to roughly 2 days 3 hours ago. 40% is its uptime for the last 6 full days, 58 of 144 hours. First sighting by Rust Analytics: 8 October 2026.
Tags & Filters
What is the meaning of the tags on typical TESTING?
Published by typical TESTING for the game's server browser to read: gmrust (Game mode): Survival in the standard Rust format; mp40 (Max players): Slot count: 40; ts8 (Group limit): 8 per team: the default setting, unchanged; v2634 (Protocol): To join, your game needs protocol 2634; cs167398 (Build): Game build: 167398; ptrak (Networking): Runs on RakNet, Rust's default network layer; $r? (Region code): No region code has been set. Also in the tags and at the top of this page: current players, queue and world creation time.
Where does typical TESTING show up in Rust Analytics lists and filters?
These Rust Analytics lists include typical TESTING: 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 to Join
How can I connect to typical TESTING?
Type client.connect 15.204.83.240:21000 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you.
Server tags
what each one meansPublished as mp40,ptrak,$r?,v2634,gmrust,cs167398,ts8
Game
gmrust
mp40
ts8
v2634
cs167398
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.