Station XX-15454 · recording
Rust Error 8
Online 45.11.16.75:28007 checked 1m ago
- Players now
- 0/ 100
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak –
- Rank
- #15,454
- top 70%
- Last wipe
- 2d ago
- no schedule published
- Next wipe
- –
- no wipe seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 100 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 19 Nov. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 70% 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 pageMap and rules
Which map is running on Rust Error 8?
Rust Error 8 runs a procedural map of size 3,500 with seed 7739282, produced by the game. Size and seed produce the same map, so RustMaps can show it from this page.
Which settings and rules apply on Rust Error 8?
The name of Rust Error 8 gives no gather rate. The group limit is 8 players, the game's default. In survival mode, the usual game of 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. Vanilla is the label it uses for itself: unchanged from Facepunch's release: no altered rates, kits or rules. VAC, Valve's anti-cheat, is switched on.
Player counts
How many players are recorded on Rust Error 8 right now?
At this moment, Rust Error 8 records 0 players across 100 slots. Averaged across the last seven days, the population was 0 players.
How does Rust Error 8 rank against other Rust servers?
The last seven days of player hours place Rust Error 8 at #15,454, in the top 70% of all ranked servers.
Server details
How reliably does Rust Error 8 stay online?
Right now, you can reach Rust Error 8. The uptime it reports puts its last restart about 2 days ago. It was up 100% of the time across the last 1 full day: 24 of 24 hours. On 19 November 2026 it was recorded for the first time by Rust Server Trends.
Does Rust Error 8 hold a steady tick rate?
Across the last 48 hours it averaged 228 server fps, with a floor of 173. Buildings, deployables and all the rest of the world's entities brought it to a high of 67,000. Memory use peaked at 2,471 MB. Low fps together with a growing entity count is what players experience as lag.
Where in the world is Rust Error 8 hosted?
A region is not published by Rust Error 8. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 45.11.16.75:28007.
What build of Rust does Rust Error 8 use?
On Linux, Rust Error 8 runs Rust network protocol 2636 and build 127089. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
How often does Rust Error 8 wipe, and on which days?
On record so far are too few of Rust Error 8's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 3 December at 19:00 UTC. It has run its current world for 2 days 4 hours.
Server tags
What do the server tags on Rust Error 8 mean?
These are the tags Rust Error 8 publishes for the browser to read: gmvanilla (Game mode): You'll find vanilla survival here; mp100 (Max players): The server has 100 slots; ts8 (Group limit): This uses the game default of 8 per team; v2636 (Protocol): Your game needs to be on protocol 2636 to join; cs127089-84fd9a97663 (Build): You won't find a published build number; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^v (Vanilla): Unchanged from Facepunch's release: no altered rates, kits or rules; ^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 Rust Error 8 appear?
You will find Rust Error 8 on the following Rust Server Trends lists: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Vanilla and Modded; Server tag: Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
Join the server
What steps get you onto Rust Error 8?
Enter client.connect 45.11.16.75:28007 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.