Rust Server TrendsSeismic network · station log
Recording Stations11,829 Players89,289 Active4,008 Wipes · 3 h41 48 h

Station XX-11606 · no signal

fuckingdelicious.org

Offline 217.160.243.217:28015 checked 7d ago

moddedoxide
Connect
Players now
1/ 20
5% full
Motion · 24 h
M –
too few hourly readings
7-day average
1
peak 1
Rank
#11,606
top 52%
Last wipe
7d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-11606 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
1of 20 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Oct22 Oct23 Oct25 Oct26 Oct28 Oct

Top 52% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak
3players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 3, 11 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Wed 21 Oct, 01:47 UTC7d ago M0.5rising 3 – running 0

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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 157 on average
205/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 127 on average
121/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 116 on average
183/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 90 on average
126/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 87 on average
19/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
50/ 1000
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on fuckingdelicious.org?

The map on fuckingdelicious.org is procedural, produced by the game.

Which settings and rules apply on fuckingdelicious.org?

You will find no gather rate in the name of fuckingdelicious.org. At the game's default, groups can have up to 8 players. It plays in survival mode, standard play, with gathering, building and raiding. You can raid and fight other players here. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.

Population

How many players are recorded on fuckingdelicious.org right now?

A reading taken now finds fuckingdelicious.org offline; the most recent activity was 7 days 2 hours ago. The seven-day average is 1 players, with a peak of 1.

How does fuckingdelicious.org rank against other Rust servers?

Over the last seven days, fuckingdelicious.org recorded enough player hours to reach #11,606 worldwide, placing it in the top 52% of all ranked servers.

Server details

How reliably does fuckingdelicious.org stay online?

As recorded now, fuckingdelicious.org is not reachable, the last contact having been 7 days 2 hours ago. It was up 11% of the time across the last 7 full days: 18 of 168 hours. On 20 October 2026 it was recorded for the first time by Rust Server Trends.

Which region does fuckingdelicious.org run from?

A region is not published by fuckingdelicious.org. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 217.160.243.217:28015.

What build of Rust does fuckingdelicious.org use?

fuckingdelicious.org is running Rust network protocol 2634 and build 167781 on a machine with Linux. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe pattern

What does wipe day look like on fuckingdelicious.org?

The recent wipes averaged a busiest count of 3 players. The peak on the most recent wipe came 11 hours after the wipe.

How often does fuckingdelicious.org wipe, and on which days?

On record so far are too few of fuckingdelicious.org's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The present world dates from 7 days 17 hours.

Lists and tags

What do the server tags on fuckingdelicious.org mean?

Tags published by fuckingdelicious.org and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp20 (Max players): 20 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167781 (Build): It runs game build 167781; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^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 fuckingdelicious.org appear?

These Rust Server Trends lists include fuckingdelicious.org: 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; Last wipe: In the last 2 weeks.

How to join

How do you connect to fuckingdelicious.org?

To join, enter client.connect 217.160.243.217:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp20,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode The game mode is standard Rust survival.
mp20
Max players 20 slots are available.
ts8
Group limit Teams max out at 8, the default set by the game.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs167781
Build It runs game build 167781.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code The server has no region code.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded The game is changed by plugins or settings, placing it under Modded.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

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.