Station XX-15335 · no signal
osmium dev rustedit-check (local)
Offline 208.88.69.27:28851 checked 6d ago
- Players now
- 0/ 4
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,335
- top 69%
- Last wipe
- 6d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 4 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 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
- 4.8 daysbetween real wipes
- wipe-day peak
- 0players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 1 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 22 Oct, 17:59 UTC6d ago | M0.0■steady | 0 | – | – | running | 0 |
| Sat 17 Oct, 23:07 UTC11d ago | M0.0■steady | 0 | – | 4.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 pageRules and settings
Which settings and rules apply on osmium dev rustedit-check (local)?
The name of osmium dev rustedit-check (local) gives no gather rate. Groups hold up to 8 players, which is the default for the game. In survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Oxide. Anti-cheat is on: VAC, from Valve.
Player counts
What is the current population on osmium dev rustedit-check (local)?
A reading taken now finds osmium dev rustedit-check (local) offline; the most recent activity was 6 days 15 hours ago. The population averaged 0 players over the past week.
How does osmium dev rustedit-check (local) rank against other Rust servers?
On player hours for the past week, osmium dev rustedit-check (local) sits at #15,335, which puts it inside the top 69% of every ranked server.
Operator and location
How reliably does osmium dev rustedit-check (local) stay online?
As recorded now, osmium dev rustedit-check (local) is not reachable, the last contact having been 6 days 15 hours ago. Of the 168 hours in the last 7 full days, it was up for 1, or 1% of the time. Its earliest appearance in the records of Rust Server Trends dates to 17 October 2026.
Where in the world is osmium dev rustedit-check (local) hosted?
A region is not published by osmium dev rustedit-check (local). The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 208.88.69.27:28851 is the address it uses.
Which Rust version is osmium dev rustedit-check (local) running?
On Linux, osmium dev rustedit-check (local) runs Rust network protocol 2634 and build 167231. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe day
What does wipe day look like on osmium dev rustedit-check (local)?
0 players, on average, was the busiest crowd at its recent wipes. 1 hours after the latest wipe, the crowd peaked.
On what timetable does osmium dev rustedit-check (local) run its wipes?
The rhythm of osmium dev rustedit-check (local) 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. The present world dates from 6 days 15 hours.
Lists and tags
What do the server tags on osmium dev rustedit-check (local) mean?
Tags published by osmium dev rustedit-check (local) and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp4 (Max players): 4 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167231 (Build): It runs game build 167231; ptrak (Networking): Network layer: RakNet, the standard for Rust; $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; osmium (Custom tag): A custom tag, not standard Rust: set by the owner or a plugin. 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 osmium dev rustedit-check (local) appear?
You will find osmium dev rustedit-check (local) on the following Rust Server Trends lists: 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 week.
Connecting
How do you connect to osmium dev rustedit-check (local)?
To join, enter client.connect 208.88.69.27:28851 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for 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.