Live coverage · NA
Offline Obsidian Dragon is not on the server list right now. The figures below are from when it was last seen, 1d ago.
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
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 27 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Embedded chart
Top 69% of all ranked servers, top 81% in NA. Ranked on player hours over the last seven days.
Coming up · wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
This server has not put up a new map since the desk started watching it.
Peak: the most players in the first 48 hours. 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.
Too few wipes are recorded for Obsidian Dragon to establish a pattern. Every server in Rust, this one among them, wipes at the monthly force wipe; Thursday 5 November at 19:00 UTC is the next. 45 hours have passed since this world was generated.
These are the Rust Live Stats lists Obsidian Dragon fits: Live Rust community servers, North America Rust servers, live and Vanilla Rust servers, live. Under the filters Region: North America; Type: Vanilla, Community (not modded, not official) and No plugins at all; Server tag: Vanilla ^v; Group limit: 5 or more; Last wipe: In the last 3 days it appears on the server list.
The server browser reads gmvanilla (Game mode): The mode is vanilla survival; mp50 (Max players): The slot count is 50; ts8 (Group limit): Team cap: 8, which is the game default; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): RakNet is the network layer — the game's standard one; $r? (Region code): The server sets no region code; ^v (Vanilla): The rates, kits and rules are unchanged from what Facepunch ships; NA (North America): North America is the browser listing for this server, which Obsidian Dragon publishes. Players now, queue length and world creation time are carried in the tags too, and appear at the top of this page.
Obsidian Dragon is not online at the moment, having last been seen 44 hours ago. The seven-day average for this server is 0 players.
Obsidian Dragon is #1,502 in North America on the past week's player hours, and #15,327 overall in the top 69% of ranked servers.
The name Obsidian Dragon carries no gather rate. No custom limit is set, so groups hold the default 8 players. survival applies here, the standard game: gather, build, raid. You can raid and fight other players. Community is its browser category. Vanilla is its own label: the rates, kits and rules are unchanged from what Facepunch ships. Anti-cheat: VAC from Valve is enabled.
The map on Obsidian Dragon is procedural, made by the game itself.
By its own NA tag, Obsidian Dragon sits in North America. A server's stated location is what Rust Live Stats shows; the machine's actual position is not looked up. 38.189.78.215:28010 is its address.
It never went below 117 server fps in the last 48 hours, averaging 117. It supported up to 14,465 entities, covering buildings, deployables and all other objects. The highest memory usage was 861 MB. Lag, as players feel it, comes from low fps and a rising entity count.
Rust network protocol 2635 and build 168909 on Linux is what Obsidian Dragon runs. Joining requires the same protocol on your game; Steam takes care of updating it.
At the time of this update, Obsidian Dragon is down, last seen 44 hours ago. The uptime it reports puts the last restart at about 19 minutes ago. 0 of 24 hours were online in the last 1 full day, giving 0% uptime. On 27 October 2026, Rust Live Stats saw it for the first time.
Use Launch Rust and join on this page to open Rust through Steam and connect, or start Rust, press F1, and type client.connect 38.189.78.215:28010.