Station XX-1481 · recording
Fudge Begynderserver(Casual Beta:Ticket on discord for access)
Online 213.32.245.243:28019 checked 6m ago
- Players now
- 0/ 50
- 0% full
- Motion · 24 h
- M0.7▼falling
- −4 players on the day
- 7-day average
- 4
- peak 18
- Rank
- #1,481
- top 7%
- Last wipe
- 6d ago
- biweekly schedule
- Next wipe
- 7d 20h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 50 slots
- Motion · 24 h
- M0.7▼falling−4 players
- Sharpest hour
- −3into Tue 23:00 UTC
- Peak · 48 h
- 7most players in any hour
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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 7% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
fixed weekdaysNext wipe Thursday 5 November, 19:00 UTC, in 7d 20h. The force wipe · high confidence
- usual gap
- 14 daysbetween real wipes
- on rhythm
- 100%of its recent wipes
- wipe-day peak
- 18players, last three wipes
- crowd held
- 0%else halves by day 3
Coming wipes
- 7d 20hThu 5 Nov, 19:00 UTCFW
- 21d 15hThu 19 Nov, 13:55 UTC
- 35d 20hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 18, 31 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 22 Oct, 13:55 UTC6d ago | M1.2▲rising | 18 | – | running | 2 | |
| Thu 15 Oct, 13:57 UTC13d ago | M1.2▲rising | 19 | halved by day 2 | 7 days | 2 | |
| Thu 1 Oct, 17:41 UTC FW27d ago | M1.2▲rising | 17 | halved by day 3 | 13.8 days | 0 | |
| Thu 17 Sep, 14:37 UTC41d ago | M1.1▲rising | 12 | halved by day 7 | 14.1 days | 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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer rules
Which map is running on Fudge Begynderserver(Casual Beta:Ticket on discord for access)?
Generated by the game, the map on Fudge Begynderserver(Casual Beta:Ticket on discord for access) is procedural, size 4,250 with seed 1766321803. You can view it on RustMaps from this page: the same size and seed produce the same map.
Which settings and rules apply on Fudge Begynderserver(Casual Beta:Ticket on discord for access)?
No gather rate appears in the name of Fudge Begynderserver(Casual Beta:Ticket on discord for access). The group limit is 8 players, the game's default. roleplay is the game mode, roleplay rules with towns and jobs. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Oxide. It describes itself as vanilla, which means unchanged from Facepunch's release: no altered rates, kits or rules. Anti-cheat is on: VAC, from Valve.
Population
What is the current population on Fudge Begynderserver(Casual Beta:Ticket on discord for access)?
A reading taken now shows 0 players on Fudge Begynderserver(Casual Beta:Ticket on discord for access), which has 50 slots. Across seven days this server recorded an average of 4 players and a peak of 18. Averaged over the last 48 hours, the busiest hour was 18:00 UTC at 6 players.
How does Fudge Begynderserver(Casual Beta:Ticket on discord for access) rank against other Rust servers?
On player hours for the past week, Fudge Begynderserver(Casual Beta:Ticket on discord for access) sits at #1,481, which puts it inside the top 7% of every ranked server.
Server facts
How reliably does Fudge Begynderserver(Casual Beta:Ticket on discord for access) stay online?
Fudge Begynderserver(Casual Beta:Ticket on discord for access) is up at the moment. The uptime it reports puts its last restart about 17 hours ago. 168 of 168 hours in the last 7 full days were up time, 100% of the total. 13 September 2026 is when Rust Server Trends first recorded it.
Does Fudge Begynderserver(Casual Beta:Ticket on discord for access) hold a steady tick rate?
Its average server fps over the last 48 hours was 94, and it never dropped below 28. The world held up to 132,771 entities at its peak, buildings and deployables included. Its highest memory use was 5,577 MB. What you feel as lag is the combination of low fps and a rising entity count.
Which region does Fudge Begynderserver(Casual Beta:Ticket on discord for access) run from?
No region is published by Fudge Begynderserver(Casual Beta:Ticket on discord for access). The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 213.32.245.243:28019.
What build of Rust does Fudge Begynderserver(Casual Beta:Ticket on discord for access) use?
On Windows, Fudge Begynderserver(Casual Beta:Ticket on discord for access) runs Rust network protocol 2635 and build 168909. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
What does wipe day look like on Fudge Begynderserver(Casual Beta:Ticket on discord for access)?
18 players, on average, was the busiest crowd at its recent wipes. 31 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 0% of its recent wipes. By day 3 it fell below half in the wipes where it didn't hold.
How often does Fudge Begynderserver(Casual Beta:Ticket on discord for access) wipe, and on which days?
every other Thursday at 13:55 UTC is how Fudge Begynderserver(Casual Beta:Ticket on discord for access) wipes. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The present world dates from 6 days 8 hours. Its tags state that it wipes every two weeks.
Tags
What do the server tags on Fudge Begynderserver(Casual Beta:Ticket on discord for access) mean?
Tags published by Fudge Begynderserver(Casual Beta:Ticket on discord for access) and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp50 (Max players): The server has 50 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): It runs game build 168909; 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; ^b (Biweekly): A wipe comes every second week; ^v (Vanilla): Unchanged from Facepunch's release: no altered rates, kits or rules; ^r (Roleplay): A server for roleplay; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does Fudge Begynderserver(Casual Beta:Ticket on discord for access) appear?
The Rust Server Trends lists that take in Fudge Begynderserver(Casual Beta:Ticket on discord for access) are: Modded Rust servers, tracked live and Rust roleplay server trends. You will find it under these filters on the server list: Type: Vanilla and Modded; Server tag: Biweekly ^b, Vanilla ^v, Roleplay ^r, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last week.
Connecting
How do you connect to Fudge Begynderserver(Casual Beta:Ticket on discord for access)?
You can connect by pressing F1 in Rust and typing client.connect 213.32.245.243:28019 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you. For the website, go to https://fudgegaming.dk/.
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.