Station XX-12095 · recording
Testserver
Online 157.85.85.43:23120 checked 11m ago
- Players now
- 0/ 1
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak 1
- Rank
- #12,095
- top 54%
- Last wipe
- 7d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 1 slots
- Motion · 24 h
- M0.0■steady+0 players
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 1 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 54% of all ranked servers. Ranked on player hours over the last seven days.
Wipe 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.
- usual gap
- 19 daysbetween real wipes
- wipe-day peak
- 1players, last three wipes
- crowd held
- 0%else halves by day 1
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 |
|---|---|---|---|---|---|---|
| Tue 20 Oct, 14:50 UTC7d ago | M0.0▲rising | 1 | – | running | 0 | |
| Thu 1 Oct, 15:21 UTC26d ago | M0.0▲rising | 1 | halved by day 1 | 19 days | 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 Testserver?
Generated by the game, the map on Testserver is procedural, size 1,500 with seed 50000. From this page you can look at it on RustMaps, since the same size and seed give the same map.
Which settings and rules apply on Testserver?
You will find no gather rate in the name of Testserver. Groups hold up to 8 players, which is the default for the game. In survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.
Live population
How many players are recorded on Testserver right now?
A reading taken now shows 0 players on Testserver, which has 1 slots. Across seven days this server recorded an average of 0 players and a peak of 1.
How does Testserver rank against other Rust servers?
Over the last seven days, Testserver recorded enough player hours to reach #12,095 worldwide, placing it in the top 54% of all ranked servers.
Server facts
How reliably does Testserver stay online?
Testserver is up at the moment. Going by the uptime figure it reports, it restarted about 4 days 18 hours ago. 168 of 168 hours in the last 7 full days were up time, 100% of the total. On 1 October 2026 it was recorded for the first time by Rust Server Trends.
How well does Testserver perform under load?
Its average server fps over the last 48 hours was 237, and it never dropped below 217. At its highest, it carried 8,458 entities: buildings, deployables and the world's other contents. It reached a ceiling of 3,472 MB of memory. What you feel as lag is the combination of low fps and a rising entity count.
Which region does Testserver run from?
Nothing about a region comes from Testserver. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 157.85.85.43:23120.
What build of Rust does Testserver use?
Testserver is running Rust network protocol 2635 and build 168909 on a machine with Linux. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
What does wipe day look like on Testserver?
1 players, on average, was the busiest crowd at its recent wipes. 0 hours into the latest wipe, the crowd reached its peak. Until the next wipe the crowd remained above half that peak in 0% of its recent wipes. By day 1 it fell below half in the wipes where it didn't hold.
How often does Testserver wipe, and on which days?
On record so far are too few of Testserver's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The present world dates from 7 days 14 hours.
Lists and tags
What do the server tags on Testserver mean?
These are the tags Testserver publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp1 (Max players): 1 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. The tags also carry its current players, its queue and when its world was made, shown 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. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Connecting
How do you connect to Testserver?
Enter client.connect 157.85.85.43:23120 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.