Fig. 1Players on Test Server (by magic)RG-S4769-01 · Sheet 1 of 11
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 18 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Fig. 2FPS, entities and memoryRG-S4769-02 · Sheet 2 of 11
Fig. 3
Rank
daily · 1 is best
RankRank in region
Top 22% of all ranked servers. Ranked on player hours over the last seven days.
Fig. 3Rank on player hours, dailyRG-S4769-03 · Sheet 3 of 11
Schedule
Wipe schedule
from its schedule tag
Next wipe Sunday 1 November, 18:22 UTC, in 3d 21h.
Its weekly schedule tag · low confidence
usual gap2.5 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak3players, last three wipes
crowd held100%of its cycles kept half the crowd
Coming wipes
3d 21hSun 1 Nov, 18:22 UTC
7d 22hThu 5 Nov, 19:00 UTCFW
10d 21hSun 8 Nov, 18:22 UTC
17d 21hSun 15 Nov, 18:22 UTC
24d 21hSun 22 Nov, 18:22 UTC
31d 21hSun 29 Nov, 18:22 UTC
35d 22hThu 3 Dec, 19:00 UTCFW
38d 21hSun 6 Dec, 18:22 UTC
The first 48 hours of its last wipes
Sun 25 OctFri 23 OctSun 18 Oct
Fig. 4Players each hour from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 4, 0 hours in.
ScheduleExpected wipesRG-S4769-04 · Sheet 4 of 11
Log
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 25 Oct, 18:22 UTC3d ago
4
–
running
3
Fri 23 Oct, 16:53 UTC5d ago
3
held half
2.1 days
2
Sun 18 Oct, 18:06 UTC10d ago
2
held half
4.9 days
0
Sun 18 Oct, 11:45 UTC10d ago
1
–
0.3 days
0
Thu 8 Oct, 16:19 UTC20d ago
4
held half
9.8 days
0
Mon 5 Oct, 17:54 UTC23d ago
2
held half
2.9 days
0
Sat 3 Oct, 15:27 UTC25d ago
1
–
2.1 days
1
Thu 1 Oct, 15:57 UTC27d ago
7
–
2 days
0
Sun 27 Sep, 15:13 UTC31d ago
4
halved by day 2
4 days
2
Thu 24 Sep, 16:45 UTC34d ago
4
held half
2.9 days
0
Fri 18 Sep, 11:56 UTC40d ago
5
halved by day 4
6.2 days
1
Tue 15 Sep, 15:46 UTC43d ago
1
–
2.8 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-S4769-05 · Sheet 5 of 11
Similar assemblies
Similar servers
the same kind of game, then region, group limit, rate and wipes
Is Test Server (by magic) online, and what uptime has been recorded?
The current state of Test Server (by magic) is offline, with the last sighting 46 hours ago. The uptime it reports puts the last restart at about 3 hours ago. 31 of 168 hours up over the last 7 full days, which is 18% of the time. On 13 September 2026 is when Rust Graphs first saw it.
2.
What does the recorded performance of Test Server (by magic) show?
Average server fps over the last 48 hours is 240; the lowest was 240. Counted at its highest: 2,613 entities, buildings, deployables and the rest of the world included. The highest memory use recorded is 777 MB. What players feel as lag is low fps together with a climbing entity count.
3.
In which location is Test Server (by magic) hosted?
No region is published by Test Server (by magic). No lookup of the machine's location is done: Rust Graphs shows where a server says it is. 212.220.0.55:28015 is its address.
4.
What Rust version is recorded for Test Server (by magic)?
The platform is Windows and the version is Rust network protocol 2635 and build 168909 on Test Server (by magic). The same protocol is required for joining, and Steam updates your game to it.
Population
5.
What does the population history show for Test Server (by magic)?
The latest refresh records Test Server (by magic) as offline, last seen 46 hours ago. Averaged across seven days, the player count is 2, with a peak of 4.
6.
What rank has been recorded for Test Server (by magic)?
Within the top 22% of all ranked servers: Test Server (by magic) at #4,769 for player hours, seven days recorded.
Schedules
7.
On Test Server (by magic), what does the data show for wipe day?
At their busiest, its recent wipes drew 3 players on average. At 0 hours after the latest wipe the crowd was at its peak. Half that peak was held until the next wipe in 100% of its recent wipes.
8.
What wipe schedule has been recorded for Test Server (by magic)?
The prediction follows its tag, because too few wipes of Test Server (by magic) are on record to confirm the schedule. Sunday 1 November at 18:22 UTC is the date its next wipe is due. The world it runs now was made 3 days 1 hours ago. The tags state a weekly wipe schedule.
Rules and settings
9.
What settings and rules apply on Test Server (by magic)?
The name of Test Server (by magic) records no gather rate. No limit is published beyond the default: 8 players per group. survival, the standard game: gather, build, raid, is the game mode. Fighting and raiding between players are enabled. Plugins or settings change the game, and the browser lists it as Modded. The plugin count is Oxide. Anti-cheat: VAC, from Valve, is on.
10.
On which map is Test Server (by magic) played?
Size 1,000 with seed 1: that is the procedural map Test Server (by magic) runs, generated by the game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map.
Filters
11.
Where does Test Server (by magic) appear among the Rust Graphs lists and filters?
The Rust Graphs lists that carry Test Server (by magic) are: Modded Rust servers. It is returned by these filters on the server list: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last week.
12.
On Test Server (by magic), what is meant by each tag?
Tags published by Test Server (by magic), and read by the game's server browser: gmrust (Game mode): Standard survival, as Rust plays; mp150 (Max players): 150 player slots; ts8 (Group limit): The team limit is 8, which is the game default; v2635 (Protocol): Your game must match protocol 2635 to join; cs168909 (Build): 168909 is the game build; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): No region code is recorded; ^w (Weekly): A wipe occurs every week; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it is listed under Modded. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.
Joining the server
13.
What is the way to connect to Test Server (by magic)?
In Rust, press F1 and type client.connect 212.220.0.55:28015 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you. https://discord.com/invite/mNrUbG4uhW is its website.
NotesAnswered from the figuresRG-S4769-10 · Sheet 10 of 11
Key
Server tags
what each one means
Published asmp150,ptrak,$r?,v2635,^w,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeStandard survival, as Rust plays.
mp150
Max players150 player slots.
ts8
Group limitThe team limit is 8, which is the game default.
v2635
ProtocolYour game must match protocol 2635 to join.
cs168909
Build168909 is the game build.
ptrak
NetworkingStandard network layer: RakNet.
$r?
Region codeNo region code is recorded.
Wipe schedule
^w
WeeklyA wipe occurs every week.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings change the game, so it is listed 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.