Station XX-15398 · no signal
typical test4
Offline 9.244.16.170:28023 checked 63d ago
- Players now
- 0/ 100
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,398
- no region published
- Last wipe
- 63d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 100 slots
- Motion · 24 h
- M –not enough readings
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 bestWipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- wipe-day peak
- 0players, 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 | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 5 Nov, 19:00 UTC FW15d ago | – | – | – | – | running | – |
| Thu 1 Oct, 18:00 UTC FW50d ago | – | – | – | – | – | – |
| Sat 19 Sep, 06:13 UTC63d ago | M0.0■steady | 0 | – | – | – | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageServer rules
Which map is running on typical test4?
typical test4 uses a procedural map, which the game generates.
Which settings and rules apply on typical test4?
No gather rate appears in the name of typical test4. Groups hold up to 8 players, which is the default for the game. In survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. It is a community server, and the browser lists it under Community. VAC, Valve's anti-cheat, is switched on.
Live population
How many players are recorded on typical test4 right now?
A reading taken now finds typical test4 offline; the most recent activity was 63 days 6 hours ago.
How does typical test4 rank against other Rust servers?
Over the last seven days, typical test4 recorded enough player hours to reach #15,398 worldwide, placing it in the top – of all ranked servers.
Server facts
How reliably does typical test4 stay online?
No contact with typical test4 right now, and the last recorded contact was 63 days 6 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. On 18 September 2026 it was recorded for the first time by Rust Server Trends.
Where in the world is typical test4 hosted?
Nothing about a region comes from typical test4. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 9.244.16.170:28023.
Which Rust version is typical test4 running?
Rust network protocol 2633 and build 164530 on Linux is what typical test4 runs. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
What does wipe day look like on typical test4?
The recent wipes averaged a busiest count of 0 players. The peak on the most recent wipe came 0 hours after the wipe.
How often does typical test4 wipe, and on which days?
The rhythm of typical test4 cannot yet be told: too few of its wipes are on record. All Rust servers wipe at the force wipe each month, the next of which is Thursday 3 December at 19:00 UTC. The present world dates from 63 days 6 hours.
Lists and tags
What do the server tags on typical test4 mean?
These are the tags typical test4 publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): Slots: 100; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2633 (Protocol): Your game needs to be on protocol 2633 to join; cs164530 (Build): The game build is 164530; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does typical test4 appear?
These Rust Server Trends lists include typical test4: Rust community servers without the side modes. You will find it under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Join the server
What steps get you onto typical test4?
Enter client.connect 9.244.16.170:28023 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.