Rust Server TrendsSeismic network · station log
Recording Stations11,733 Players63,580 Active3,313 Wipes · 3 h197 48 h

Station EU-14176 · recording

Fuchshöhle

Online EU 193.135.10.247:15010 checked 11m ago

moddedoxidepve
Connect
Players now
0/ 20
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 1
Rank
#14,176
top 64% · #2440 in EU
Last wipe
28d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station EU-14176 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 20 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
+0into Wed 19:00 UTC
Peak · 48 h
1most players in any hour
Channel 1 · calibrated

Players

AveragePeak
00.250.50.75101:0016:0020:0022:0001:0022:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

02040608001:0016:0020:0022:0001:0022:00

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 22 Sep. 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
15k10k15k20k22 Sep29 Sep7 Oct14 Oct22 Oct29 Oct

Top 64% of all ranked servers, top 84% in EU. 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.

usual gap
0.3 daysbetween real wipes
wipe-day peak
2players, last three wipes

The first 48 hours of its last wipes

Thu 1 OctThu 1 Oct
00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 1 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Thu 1 Oct, 18:11 UTC FW28d ago M0.3rising 2 – running 0
Thu 1 Oct, 11:46 UTC28d ago M0.0steady 2 – 0.3 days 2

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
[EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo EU · no group limit · biweekly · 242 on average
168/ 2000
TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 EU · groups of 30+ · biweekly · 49 on average
20/ 100
1[PvE]Тульский|Русский|Classic+Ивенты EU · groups of 8+ · monthly · 33 on average
9/ 200
[PvE] Relic Europe | No Killing | No Raiding | No Decay EU · groups of 30+ · monthly · 31 on average
22/ 200
[GER] Rust Oase |PVE|Quests|XP|Raidable Bases|Events EU · groups of 15+ · monthly · 28 on average
15/ 140
[EU/US] RustyWasteland PVE | Fun Week | Zombies | RaidBases EU · groups of 10+ · biweekly · 26 on average
38/ 100
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on Fuchshöhle?

Generated by the game, the map on Fuchshöhle is procedural, size 5,000 with seed 12345. From this page you can look at it on RustMaps, since the same size and seed give the same map.

Which settings and rules apply on Fuchshöhle?

No gather rate appears in the name of Fuchshöhle. The group limit is 8 players, the game's default. In pve mode, no combat against other players. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.

Live population

What is the current population on Fuchshöhle?

0 of the 20 slots on Fuchshöhle are filled right now. Across seven days this server recorded an average of 0 players and a peak of 1. The last 48 hours show their highest activity at 19:00 UTC, averaging 0 players.

How does Fuchshöhle rank against other Rust servers?

The last seven days of player hours place Fuchshöhle at #14,176, in the top 64% of all ranked servers and #2,440 in Europe.

Server details

How reliably does Fuchshöhle stay online?

As recorded now, Fuchshöhle is running. The uptime it reports puts its last restart about 1 hours ago. Of the 168 hours in the last 7 full days, it was up for 130, or 77% of the time. 22 September 2026 is when Rust Server Trends first recorded it.

Does Fuchshöhle hold a steady tick rate?

The 48-hour average is 51 server fps; 42 is the lowest observed. At its highest, it carried 156,884 entities: buildings, deployables and the world's other contents. It reached a ceiling of 4,392 MB of memory. What you feel as lag is the combination of low fps and a rising entity count.

Where in the world is Fuchshöhle hosted?

In Europe Fuchshöhle lists itself, with the tag EU. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 193.135.10.247:15010.

What build of Rust does Fuchshöhle use?

On Linux, Fuchshöhle runs Rust network protocol 2635 and build 168909. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe day

What does wipe day look like on Fuchshöhle?

2 players, on average, was the busiest crowd at its recent wipes. 1 hours into the latest wipe, the crowd reached its peak.

On what timetable does Fuchshöhle run its wipes?

The rhythm of Fuchshöhle cannot yet be told: too few of its wipes are on record. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 28 days 4 hours.

Server tags

What do the server tags on Fuchshöhle mean?

These are the tags Fuchshöhle publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp20 (Max players): Slots: 20; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): Game build: 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^p (PvE): The danger comes from the world, not from other players; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; EU (Europe): In the server browser it appears under Europe. 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 Fuchshöhle appear?

These Rust Server Trends lists include Fuchshöhle: EU Rust servers, Modded Rust servers, tracked live and Rust PvE servers. You will find it under these filters on the server list: Region: Europe; Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.

Join the server

How do you connect to Fuchshöhle?

To join, enter client.connect 193.135.10.247:15010 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. For the website, go to https://tonfuchs.space.

Instrument codes

Server tags

what each one means

Published as mp20,ptrak,$r?,v2635,^p,EU,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival in standard Rust.
mp20
Max players Slots: 20.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2635
Protocol To connect, your game must be on the same protocol, 2635.
cs168909
Build Game build: 168909.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code The server has no region code.

Gameplay

^p
PvE The danger comes from the world, not from other players.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded Plugins or settings alter the game, so it's listed under Modded.

Region

EU
Europe In the server browser it appears under Europe.

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.