Station XX-12140 · no signal
JDAVID56
Offline 129.222.59.31:28015 checked 21d ago
- Players now
- 2/ 10
- 20% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #12,140
- top 55%
- Last wipe
- 21d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 2of 10 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 55% 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.
- wipe-day peak
- 2players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 2 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Wed 7 Oct, 19:52 UTC21d ago | M0.0▲rising | 2 | – | running | 1 |
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 pageMap and rules
Which map is running on JDAVID56?
A procedural map runs on JDAVID56, generated by the game.
Which settings and rules apply on JDAVID56?
You will find no gather rate in the name of JDAVID56. At the game's default, groups can have up to 8 players. In survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. Anti-cheat is on: VAC, from Valve.
Live population
What is the current population on JDAVID56?
A reading taken now finds JDAVID56 offline; the most recent activity was 21 days 11 hours ago.
How does JDAVID56 rank against other Rust servers?
On player hours for the past week, JDAVID56 sits at #12,140, which puts it inside the top 55% of every ranked server.
Server facts
How reliably does JDAVID56 stay online?
As recorded now, JDAVID56 is not reachable, the last contact having been 21 days 11 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. 7 October 2026 is when Rust Server Trends first recorded it.
Which region does JDAVID56 run from?
A region is not published by JDAVID56. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 129.222.59.31:28015 is the address it uses.
Which Rust version is JDAVID56 running?
JDAVID56 is running Rust network protocol 2634 and build 167058 on a machine with Windows. 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 JDAVID56?
The recent wipes averaged a busiest count of 2 players. 2 hours into the latest wipe, the crowd reached its peak.
On what timetable does JDAVID56 run its wipes?
The rhythm of JDAVID56 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 21 days 16 hours.
Tags
What do the server tags on JDAVID56 mean?
These are the tags JDAVID56 publishes for the browser to read: gmvanilla (Game mode): This is vanilla survival; mp10 (Max players): Slots: 10; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs167058 (Build): Game build: 167058; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does JDAVID56 appear?
These Rust Server Trends lists include JDAVID56: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Connecting
What steps get you onto JDAVID56?
Enter client.connect 129.222.59.31:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust 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.