Station XX-15848 · no signal
osmium dev render-c (local)
Offline 208.88.69.27:28990 checked 20d ago
- Players now
- 0/ 4
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,848
- top 72%
- Last wipe
- 20d ago
- no schedule published
- Next wipe
- –
- no wipe 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 72% 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 osmium dev render-c (local)?
The map on osmium dev render-c (local) is procedural, produced by the game.
Which settings and rules apply on osmium dev render-c (local)?
The name of osmium dev render-c (local) gives no gather rate. At the game's default, groups can have up to 8 players. It plays 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
How many players are recorded on osmium dev render-c (local) right now?
osmium dev render-c (local) is not responding at this moment and is offline, last seen 20 days 23 hours ago.
How does osmium dev render-c (local) rank against other Rust servers?
On player hours for the past week, osmium dev render-c (local) sits at #15,848, which puts it inside the top 72% of every ranked server.
Server details
How reliably does osmium dev render-c (local) stay online?
As recorded now, osmium dev render-c (local) is not reachable, the last contact having been 20 days 23 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 8 October 2026.
Which region does osmium dev render-c (local) run from?
No region is published by osmium dev render-c (local). Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 208.88.69.27:28990.
Which Rust version is osmium dev render-c (local) running?
osmium dev render-c (local) is running Rust network protocol 2634 and build 167231 on a machine with Linux. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe pattern
How often does osmium dev render-c (local) wipe, and on which days?
The rhythm of osmium dev render-c (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. It has run its current world for 20 days 23 hours.
Server tags
What do the server tags on osmium dev render-c (local) mean?
Tags published by osmium dev render-c (local) and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp4 (Max players): The server has 4 slots; 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): The network layer is RakNet, the game's standard; $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 osmium dev render-c (local) appear?
You will find osmium dev render-c (local) on the following Rust Server Trends lists: 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
What steps get you onto osmium dev render-c (local)?
You can connect by pressing F1 in Rust and typing client.connect 208.88.69.27:28990 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.