Fig. 1Players on Fudge PvE TestserverRG-S13075-01 · Sheet 1 of 10
Fig. 2
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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.
Fig. 2FPS, entities and memoryRG-S13075-02 · Sheet 2 of 10
Fig. 3
Rank
daily · 1 is best
RankRank in region
Top 60% of all ranked servers. Ranked on player hours over the last seven days.
Fig. 3Rank on player hours, dailyRG-S13075-03 · Sheet 3 of 10
Schedule
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap4 daysbetween real wipes
on rhythm29%of its recent wipes
wipe-day peak3players, last three wipes
crowd held100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Wed 14 OctSat 10 OctSat 10 Oct
Fig. 4Players each hour from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
ScheduleExpected wipesRG-S13075-04 · Sheet 4 of 10
Log
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Wed 14 Oct, 12:08 UTC15d ago
1
–
running
0
Sat 10 Oct, 23:59 UTC18d ago
4
held half
3.5 days
4
Sat 10 Oct, 00:12 UTC19d ago
5
–
1 days
3
Mon 5 Oct, 02:01 UTC24d ago
4
held half
4.9 days
2
Fri 2 Oct, 12:05 UTC27d ago
4+1 queue
held half
2.6 days
1
Mon 28 Sep, 12:43 UTC31d ago
1
–
4 days
0
Sun 20 Sep, 15:51 UTC39d ago
1
halved by day 3
7.9 days
1
Sun 13 Sep, 13:00 UTC46d ago
3
halved by day 4
7.1 days
1
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.
Table 1Wipe logRG-S13075-05 · Sheet 5 of 10
Similar assemblies
Similar servers
the same kind of game, then region, group limit, rate and wipes
What uptime is recorded for Fudge PvE Testserver, and is it up?
The current state of Fudge PvE Testserver is offline, with the last sighting 11 days 12 hours ago. For the last 7 full days the record is 0 of 168 hours up, 0% of the time. On 13 September 2026 is when Rust Graphs first saw it.
2.
What location is recorded for Fudge PvE Testserver?
There is no region published by Fudge PvE Testserver. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. It is reached at 213.32.245.243:28317.
3.
What Rust version is recorded for Fudge PvE Testserver?
The platform is Windows and the version is Rust network protocol 2634 and build 166586 on Fudge PvE Testserver. Steam updates your game, which must be on the same protocol for you to join.
Counts
4.
What player count is recorded on Fudge PvE Testserver?
No response from Fudge PvE Testserver; the server was last seen 11 days 12 hours ago.
5.
Against other Rust servers, where is Fudge PvE Testserver placed?
Within the top 60% of all ranked servers: Fudge PvE Testserver at #13,075 for player hours, seven days recorded.
Wipe data
6.
What happens on Fudge PvE Testserver on the day of a wipe?
At their busiest, its recent wipes drew 3 players on average. At 0 hours after the latest wipe the crowd was at its peak. Up to the next wipe, the crowd in 100% of its recent wipes stayed above half that peak.
7.
What wipe schedule has been recorded for Fudge PvE Testserver?
Fudge PvE Testserver wipes at times that follow no pattern, so no next wipe can be predicted. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. 18 days 20 hours ago the current world was made.
Settings
8.
Which rules and settings are recorded for Fudge PvE Testserver?
No gather rate is stated in the name of Fudge PvE Testserver. Eight players per group: the default for the game. It runs the survival game mode, the standard game: gather, build, raid. PvP and raiding are on. Listed as Modded in the server browser: the game is changed by plugins or settings. Oxide plugins are run on it. VAC is on: that is Valve's anti-cheat.
9.
What is the map for Fudge PvE Testserver?
Seed 128664991 and size 4,250 define the procedural map Fudge PvE Testserver generates in game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map.
Tags
10.
On Rust Graphs, which lists and filters contain Fudge PvE Testserver?
On Rust Graphs, Fudge PvE Testserver is placed in these lists: Modded Rust servers. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
11.
On Fudge PvE Testserver, what is meant by each tag?
The game's server browser reads these tags from Fudge PvE Testserver: gmrust (Game mode): Survival in standard Rust style; mp0 (Max players): Slots: 0; ts8 (Group limit): The team limit is 8, which is the game default; v2634 (Protocol): Join only if your game is on protocol 2634; cs166586 (Build): Build: 166586; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): No region code is recorded; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.
How to join
12.
What is the way to connect to Fudge PvE Testserver?
Enter client.connect 213.32.245.243:28317 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you. https://fudgegaming.dk/ is its website.
NotesAnswered from the figuresRG-S13075-09 · Sheet 9 of 10
Key
Server tags
what each one means
Published asmp0,ptrak,$r?,v2634,gmrust,cs166586,ts8,^o^z
Game
gmrust
Game modeSurvival in standard Rust style.
mp0
Max playersSlots: 0.
ts8
Group limitThe team limit is 8, which is the game default.
v2634
ProtocolJoin only if your game is on protocol 2634.
cs166586
BuildBuild: 166586.
ptrak
NetworkingStandard network layer: RakNet.
$r?
Region codeNo region code is recorded.
Mods and access
^o
OxideThe plugin framework is Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; the listing is 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.
KeyTag string decodedRG-S13075-10 · Sheet 10 of 10