Station XX-14542 · no signal
LocalRustServer1337
Offline 90.154.73.85:28015 checked 30d ago
- Players now
- 1/ 10
- 10% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #14,542
- top 61%
- Last wipe
- 32d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 10 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 61% 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
- 0.9 daysbetween real wipes
- on rhythm
- 0%of its recent wipes
- wipe-day peak
- 1players, last three wipes
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 |
|---|---|---|---|---|---|---|
| Sat 26 Sep, 12:10 UTC32d ago | M0.0■steady | 1 | – | running | 1 | |
| Fri 25 Sep, 11:15 UTC33d ago | M0.0■steady | 1 | – | 1 days | 1 | |
| Thu 24 Sep, 17:50 UTC33d ago | M0.0■steady | 1 | – | 0.7 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 LocalRustServer1337?
A procedural map runs on LocalRustServer1337, generated by the game.
Which settings and rules apply on LocalRustServer1337?
The name of LocalRustServer1337 gives no gather rate. The group limit is 8 players, the game's default. survival is the game 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. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched off.
Player counts
What is the current population on LocalRustServer1337?
A reading taken now finds LocalRustServer1337 offline; the most recent activity was 30 days 22 hours ago.
How does LocalRustServer1337 rank against other Rust servers?
Over the last seven days, LocalRustServer1337 recorded enough player hours to reach #14,542 worldwide, placing it in the top 61% of all ranked servers.
Operator and location
How reliably does LocalRustServer1337 stay online?
No contact with LocalRustServer1337 right now, and the last recorded contact was 30 days 22 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. 23 September 2026 is when Rust Server Trends first recorded it.
Which region does LocalRustServer1337 run from?
No region is published by LocalRustServer1337. 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 90.154.73.85:28015.
Which Rust version is LocalRustServer1337 running?
Rust network protocol 2633 and build 165217 on Windows is what LocalRustServer1337 runs. The protocol must match for you to join, and Steam takes care of updating it.
Wipe pattern
What does wipe day look like on LocalRustServer1337?
On average, the busiest point of its recent wipes drew 1 players. The peak on the most recent wipe came 0 hours after the wipe.
On what timetable does LocalRustServer1337 run its wipes?
No next wipe can be predicted for LocalRustServer1337, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 32 days 1 hours.
Tags
What do the server tags on LocalRustServer1337 mean?
The game's server browser reads the tags LocalRustServer1337 publishes: gmrust (Game mode): You'll find standard Rust survival here; mp10 (Max players): Slots: 10; ts8 (Group limit): This uses the game default of 8 per team; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs165217 (Build): The game build is 165217; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it 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 LocalRustServer1337 appear?
These Rust Server Trends lists include LocalRustServer1337: 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.
Connecting
How do you connect to LocalRustServer1337?
You can connect by pressing F1 in Rust and typing client.connect 90.154.73.85: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.