Station XX-13797 · no signal
TestServerSolo
Offline 138.219.94.130:28015 checked 26d ago
- Players now
- 1/ 1
- 100% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #13,797
- top 60%
- Last wipe
- 26d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 1 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 bestTop 60% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
- usual gap
- 0.6 daysbetween real wipes
- on rhythm
- 0%of its recent wipes
- wipe-day peak
- 1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Fri 2 Oct, 16:07 UTC26d ago | M0.0▲rising | 1 | – | – | running | 0 |
| Thu 1 Oct, 18:19 UTC FW27d ago | M0.0■steady | 1 | – | 0.9 days | 1 | |
| Thu 1 Oct, 11:27 UTC28d ago | M0.0■steady | 1 | – | 0.3 days | 1 |
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 pageMap and rules
Which map is running on TestServerSolo?
A procedural map runs on TestServerSolo, generated by the game.
Which settings and rules apply on TestServerSolo?
You will find no gather rate in the name of TestServerSolo. The group limit is 8 players, the game's default. In survival mode, standard play, with gathering, building and raiding. You can raid and fight other players here. It is a community server, and the browser lists it under Community. VAC, Valve's anti-cheat, is switched on.
Live population
What is the current population on TestServerSolo?
A reading taken now finds TestServerSolo offline; the most recent activity was 26 days 22 hours ago.
How does TestServerSolo rank against other Rust servers?
The last seven days of player hours place TestServerSolo at #13,797, in the top 60% of all ranked servers.
Server details
How reliably does TestServerSolo stay online?
No contact with TestServerSolo right now, and the last recorded contact was 26 days 22 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 29 September 2026 is when Rust Server Trends first recorded it.
Where in the world is TestServerSolo hosted?
Nothing about a region comes from TestServerSolo. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 138.219.94.130:28015 is the address it uses.
What build of Rust does TestServerSolo use?
TestServerSolo is running Rust network protocol 2634 and build 166586 on a machine with Windows. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe day
What does wipe day look like on TestServerSolo?
On average, the busiest point of its recent wipes drew 1 players. 0 hours after the latest wipe, the crowd peaked.
How often does TestServerSolo wipe, and on which days?
No next wipe can be predicted for TestServerSolo, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 26 days 23 hours.
Server tags
What do the server tags on TestServerSolo mean?
These are the tags TestServerSolo publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp1 (Max players): The server has 1 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs166586 (Build): Game build: 166586; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does TestServerSolo appear?
The Rust Server Trends lists that take in TestServerSolo are: 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.
Connecting
How do you connect to TestServerSolo?
Enter client.connect 138.219.94.130:28015 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.