danji
Offline EA 59.51.118.167:28015 checked 34d ago
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 bestWipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 18d 9h. The force wipe
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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.
Similar servers
the same kind of game, then region, group limit, rate and wipes
- 3/ 100
- 2/ 100
- 5/ 188
- 4/ 32
- 2/ 233
- 2/ 50
Quick answers
Tags and filters
Where does danji appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry danji are: Modded Rust servers. The server list shows it under Region: Asia; Type: Vanilla and Modded; Server tag: Monthly ^m, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
What's the meaning of the tags on danji?
gmrust (Game mode): This is the standard Rust survival experience; mp1 (Max players): It holds 1 players; ts8 (Group limit): It uses the default team limit: 8; v2633 (Protocol): To join, your game has to be on protocol 2633; cs163794 (Build): This server runs build 163794; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): It has no region code; ^m (Monthly): Monthly wipes, timed with the Facepunch force wipe; ^v (Vanilla): It's the vanilla game: rates, kits and rules are all standard; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): Plugins or settings make changes, so it's listed as Modded; EA (East Asia): In the server browser it appears under East Asia — that is the tag list danji puts out for the game's server browser. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
Server details
What location is danji in?
The EA tag marks danji as being in Asia. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. You can reach it at 59.51.118.167:28015.
What's the uptime like for danji?
The server danji is not reachable at the moment; the last sighting was 34 days 22 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. Rust Going Deep has had it on record since 13 September 2026.
What is the Rust version for danji?
The version on danji is Rust network protocol 2633 and build 163794, on Windows. The protocol must match to join; Steam will update your game.
Wipe schedule
What schedule does danji follow for wipes?
An estimate from the force wipe gives danji's next wipe. When every Rust server wipes on Thursday 5 November at 19:00 UTC, that force wipe is its next wipe. 34 days 23 hours is how long ago this world came into being. Its tags publish a wipe schedule that runs monthly.
Map and rules
Which rules and settings is danji running?
No gather rate appears in the name of danji. Up to 8 players per group, which is the default. survival is the game mode, gather, build and raid, the standard game. You can fight and raid other players. The server browser puts it under Modded, as plugins or settings alter the game. Oxide plugins are running here. Its own word for it is vanilla: it's the vanilla game: rates, kits and rules are all standard. VAC, Valve's anti-cheat, is disabled.
Which map is active on danji?
A procedural map, generated by the game, is in play on danji.
Player count
What's the population like on danji?
danji was last seen 34 days 22 hours ago and is offline as you read this.
Join info
How do you get into danji?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 59.51.118.167:28015.