Station XX-13052 · no signal
TestServ
Offline 5.68.240.132:28015 checked 10d ago
- Players now
- 1/ 500
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #13,052
- top 59%
- Last wipe
- 24d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 500 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 59% 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.6 daysbetween real wipes
- on rhythm
- 0%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 |
|---|---|---|---|---|---|---|
| Fri 9 Oct, 04:15 UTC19d ago | M0.0■steady | 1 | – | running | 1 | |
| Sun 4 Oct, 06:16 UTC24d ago | M0.0▲rising | 1 | held half | 4.9 days | 0 | |
| Sat 3 Oct, 21:52 UTC24d ago | M0.0■steady | 1 | – | 0.4 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 TestServ?
TestServ uses a procedural map, which the game generates.
Which settings and rules apply on TestServ?
You will find no gather rate in the name of TestServ. At the game's default, groups can have up to 8 players. It plays in survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Community, as a community server. Anti-cheat is on: VAC, from Valve.
Live population
What is the current population on TestServ?
TestServ is not responding at this moment and is offline, last seen 10 days 9 hours ago.
How does TestServ rank against other Rust servers?
On player hours for the past week, TestServ sits at #13,052, which puts it inside the top 59% of every ranked server.
Operator and location
How reliably does TestServ stay online?
No contact with TestServ right now, and the last recorded contact was 10 days 9 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. Its earliest appearance in the records of Rust Server Trends dates to 19 September 2026.
Where in the world is TestServ hosted?
No region is published by TestServ. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 5.68.240.132:28015 is the address it uses.
Which Rust version is TestServ running?
Rust network protocol 2634 and build 167781 on Windows is what TestServ runs. The protocol must match for you to join, and Steam takes care of updating it.
Wipe schedule
What does wipe day look like on TestServ?
1 players, on average, was the busiest crowd at its recent wipes. 0 hours after the latest wipe, the crowd peaked. Until the next wipe the crowd remained above half that peak in 100% of its recent wipes.
How often does TestServ wipe, and on which days?
No next wipe can be predicted for TestServ, which wipes at irregular times. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 24 days 8 hours.
Lists and tags
What do the server tags on TestServ mean?
These are the tags TestServ publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp500 (Max players): 500 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167781 (Build): Game build: 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code. 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 TestServ appear?
The Rust Server Trends lists that take in TestServ are: Rust community servers without the side modes. 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.
Join the server
What steps get you onto TestServ?
Enter client.connect 5.68.240.132: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.