Station XX-15349 · recording
My Rust server | Powered by AMP
Online 178.143.12.37:28015 checked 12m ago
- Players now
- 0/ 1000
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak –
- Rank
- #15,349
- top 69%
- Last wipe
- 23d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 1000 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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 69% 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
- 8 daysbetween real wipes
- wipe-day peak
- 2players, last three wipes
- crowd held
- 0%else halves by day 5
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 28 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Mon 5 Oct, 14:32 UTC23d ago | M0.5▲rising | 3 | – | running | 0 | |
| Sun 27 Sep, 13:36 UTC31d ago | M0.3▲rising | 2 | halved by day 5 | 8 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 pageMap and rules
Which map is running on My Rust server | Powered by AMP?
My Rust server | Powered by AMP uses a procedural map, which the game generates.
Which settings and rules apply on My Rust server | Powered by AMP?
The name of My Rust server | Powered by AMP gives no gather rate. The group limit is 8 players, the game's default. survival is the game 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 My Rust server | Powered by AMP right now?
0 of the 1,000 slots on My Rust server | Powered by AMP are filled right now. The population averaged 0 players over the past week.
How does My Rust server | Powered by AMP rank against other Rust servers?
On player hours for the past week, My Rust server | Powered by AMP sits at #15,349, which puts it inside the top 69% of every ranked server.
Server details
How reliably does My Rust server | Powered by AMP stay online?
As recorded now, My Rust server | Powered by AMP is running. Of the 168 hours in the last 7 full days, it was up for 167, or 99% of the time. On 13 September 2026 it was recorded for the first time by Rust Server Trends.
Which region does My Rust server | Powered by AMP run from?
Nothing about a region comes from My Rust server | Powered by AMP. 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 178.143.12.37:28015.
What build of Rust does My Rust server | Powered by AMP use?
My Rust server | Powered by AMP is running Rust network protocol 2634 and build 166652 on a machine with Linux. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe schedule
What does wipe day look like on My Rust server | Powered by AMP?
The recent wipes averaged a busiest count of 2 players. 28 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 0% of its recent wipes. By day 5 it fell below half in the wipes where it didn't hold.
On what timetable does My Rust server | Powered by AMP run its wipes?
The rhythm of My Rust server | Powered by AMP cannot yet be told: too few of its wipes are on record. 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 23 days 7 hours.
Tags
What do the server tags on My Rust server | Powered by AMP mean?
These are the tags My Rust server | Powered by AMP publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp1000 (Max players): Slots: 1,000; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs166652 (Build): The game build is 166652; 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. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does My Rust server | Powered by AMP appear?
These Rust Server Trends lists include My Rust server | Powered by AMP: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How to join
How do you connect to My Rust server | Powered by AMP?
Enter client.connect 178.143.12.37: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.