LiveLive coverage · Rust server
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 3 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Embedded chart
Top 69% of all ranked servers. 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 dragonaxe 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. The world you are playing on was built 25 days 13 hours.
These are the Rust Live Stats lists dragonaxe fits: Modded Rust servers live now. These filters on the server list bring it up: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
The server browser reads gmrust (Game mode): Standard survival, in the Rust style; mp40 (Max players): 40 slots are available; ts8 (Group limit): 8 per team at most, the game's default setting; v2634 (Protocol): Join only if your game is on protocol 2634; cs166652 (Build): Build: 166652; ptrak (Networking): RakNet, the game's usual network layer, carries this server; $r? (Region code): The server sets no region code; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; ^z (Modded): Modded: plugins or changed settings alter the game, which dragonaxe publishes. The current player count, the queue and the world's creation time also sit in the tags, shown at the top of this page.
0 of dragonaxe's 40 slots are filled right now. Across the past week the average was 0 players.
On player hours for the past seven days, dragonaxe sits at #15,432, inside the top 69% of ranked servers.
The name dragonaxe 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. Raiding and player combat are both permitted. Plugins or settings change the game, and the browser lists it as Modded. Oxide plugins are in use. VAC is enabled: Valve's anti-cheat.
A procedural map of 2,000 with seed 625958253, generated by the game, runs on dragonaxe. RustMaps shows it from this page, since equal size and seed give an equal map.
There is no region from dragonaxe. Where the machine stands is not checked by Rust Live Stats; only the location a server states is shown. You can reach it at 64.40.8.121:28115.
Server fps averaged 5 over the last 48 hours, with a low of 5. It supported up to 13,442 entities, covering buildings, deployables and all other objects. The highest memory usage was 1,793 MB. Players experience lag when fps is low and the entity count climbs.
dragonaxe operates on Linux with Rust network protocol 2634 and build 166652. Joining requires the same protocol on your game; Steam takes care of updating it.
At the time of this update, dragonaxe is live. Based on the uptime it reports, the last restart was about 25 days 12 hours ago. 168 of 168 hours were online in the last 7 full days, giving 100% uptime. On 3 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 64.40.8.121:28115.