Station XX-6599 · no signal
Local Test Server
Offline 2.135.124.80:28015 checked 1d ago
- Players now
- 0/ 15
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 1
- peak 1
- Rank
- #6,599
- top 30%
- Last wipe
- 22d ago
- no schedule published
- Next wipe
- –
- no wipe seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 15 slots
- Motion · 24 h
- M0.0■steady+0 players
- Sharpest hour
- +1into Tue 13:00 UTC
- Peak · 48 h
- 1most players in any hour
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 17 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 30% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
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 Local Test Server?
Local Test Server runs a procedural map of size 3,750 with seed 12345, produced by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.
Which settings and rules apply on Local Test Server?
You will find no gather rate in the name of Local Test Server. The group limit is 8 players, the game's default. survival is the game mode, gather, build and raid in the standard game. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Oxide. The server has VAC on, Valve's anti-cheat.
Population
How many players are recorded on Local Test Server right now?
A reading taken now finds Local Test Server offline; the most recent activity was 26 hours ago. The seven-day average is 1 players, with a peak of 1. Averaged over the last 48 hours, the busiest hour was 13:00 UTC at 1 players.
How does Local Test Server rank against other Rust servers?
On player hours for the past week, Local Test Server sits at #6,599, which puts it inside the top 30% of every ranked server.
Server facts
How reliably does Local Test Server stay online?
Local Test Server is down at the moment; the last recorded contact was 26 hours ago. Its reported uptime points to a restart about 17 hours ago. Of the 168 hours in the last 7 full days, it was up for 23, or 14% of the time. 17 October 2026 is when Rust Server Trends first recorded it.
Does Local Test Server hold a steady tick rate?
Across the last 48 hours it averaged 123 server fps, with a floor of 94. At its highest, it carried 80,191 entities: buildings, deployables and the world's other contents. Memory use peaked at 2,330 MB. Low fps together with a growing entity count is what players experience as lag.
Which region does Local Test Server run from?
Nothing about a region comes from Local Test Server. 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 2.135.124.80:28015.
Which Rust version is Local Test Server running?
On Windows, Local Test Server runs Rust network protocol 2635 and build 168909. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
How often does Local Test Server wipe, and on which days?
Too few wipes of Local Test Server are on record yet to show its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 22 days 19 hours.
Server tags
What do the server tags on Local Test Server mean?
The game's server browser reads the tags Local Test Server publishes: gmrust (Game mode): You'll find standard Rust survival here; mp15 (Max players): 15 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^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 Local Test Server appear?
These Rust Server Trends lists include Local Test Server: 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 Local Test Server?
You can connect by pressing F1 in Rust and typing client.connect 2.135.124.80: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.