Station XX-13631 · no signal
TestServer
Offline 90.204.149.14:28015 checked 17d ago
- Players now
- 1/ 10
- 10% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #13,631
- top 62%
- Last wipe
- 17d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 10 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 62% 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
- 2.1 daysbetween real wipes
- on rhythm
- 50%of its recent wipes
- wipe-day peak
- 1players, last three wipes
- crowd held
- 100%of its cycles kept half the crowd
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 |
|---|---|---|---|---|---|---|
| Sat 10 Oct, 16:19 UTC17d ago | M0.0■steady | 1 | – | – | running | 1 |
| Thu 8 Oct, 09:17 UTC20d ago | M0.0▲rising | 1 | held half | 2.3 days | 0 | |
| Tue 6 Oct, 10:47 UTC22d ago | M0.0■steady | 1 | – | 1.9 days | 1 | |
| Sat 3 Oct, 10:32 UTC25d ago | M0.0■steady | 1 | held half | 3 days | 1 | |
| Fri 2 Oct, 13:07 UTC25d ago | M0.0■steady | 1 | – | 0.9 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 pageRules and settings
Which map is running on TestServer?
A procedural map runs on TestServer, generated by the game.
Which settings and rules apply on TestServer?
The name of TestServer gives no gather rate. At the game's default, groups can have up to 8 players. In survival mode, standard play, with gathering, building and raiding. You can raid and fight other players here. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Oxide. The server has VAC on, Valve's anti-cheat.
Player counts
How many players are recorded on TestServer right now?
A reading taken now finds TestServer offline; the most recent activity was 17 days 18 hours ago.
How does TestServer rank against other Rust servers?
On player hours for the past week, TestServer sits at #13,631, which puts it inside the top 62% of every ranked server.
Operator and location
How reliably does TestServer stay online?
TestServer is down at the moment; the last recorded contact was 17 days 18 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 1 October 2026 it was recorded for the first time by Rust Server Trends.
Where in the world is TestServer hosted?
No region is published by TestServer. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 90.204.149.14:28015.
Which Rust version is TestServer running?
TestServer is running Rust network protocol 2634 and build 167398 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 TestServer?
The recent wipes averaged a busiest count of 1 players. 0 hours into the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.
How often does TestServer wipe, and on which days?
No next wipe can be predicted for TestServer, which wipes at irregular times. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 17 days 18 hours.
Tags
What do the server tags on TestServer mean?
These are the tags TestServer publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp10 (Max players): Slots: 10; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167398 (Build): The game build is 167398; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. 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 TestServer appear?
The Rust Server Trends lists that take in TestServer are: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Join the server
How do you connect to TestServer?
You can connect by pressing F1 in Rust and typing client.connect 90.204.149.14:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game 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.