Statistical profileOnline
Test
24.113.60.221:28015 checked 12m ago
Connect to this server
1. Main points
Players now
0/ 50
0% full
7-day average
0
peak 2
Rank
#7,688
top 35%
Last wipe
1d ago
no schedule published
Next wipe
–
no rhythm it keeps
Main points
- There were 0 players on it, 0% of its 50 slots.
- Over the last seven days it averaged 0 players, with a peak of 2.
- It ranks #7,688 of all ranked servers, the top 35%, on player hours over the last seven days.
- Its current map went up 1d ago.
2. Players
Figure 1: Players on Test
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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 27 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 35% of all ranked servers. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Patternno 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 gap
13 days
between real wipes
On rhythm
0%
of its recent wipes
Wipe-day peak
4
players, last three wipes
Crowd held
50%
else halves by day 8
Figure 4: The first 48 hours of its last wipes
Players each hour, from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 3, 0 hours in.
Source: Live server queries, Rust Census
6. Wipes
Table 1: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Wed 28 Oct, 03:08 UTC1d ago | – | – | running | 0 |
| Sun 11 Oct, 03:49 UTC18d ago | 3 | halved by day 8 | 17 days | 3 |
| Fri 2 Oct, 04:27 UTC26d ago | 5 | held half | 9 days | 0 |
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
Figure 5: Map of Test
4500 · seed 62803
8. Server characteristics
Table 3: Characteristics of Test
What the server publishes and what was recorded
| Address | 24.113.60.221:28015 |
|---|---|
| Region | – |
| Max players | 50 |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 28 Oct 2026, 03:08 UTC |
| Hostname | – |
| First seen | 27 Sep 2026 |
9. Similar servers
Table 4: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| ShockRust | Blue | NoLimit | no group limit · 153 on average | 36 / 500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 124 / 100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 42 / 225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 10 / 700 |
| RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 1 / 200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 0 / 1000 |
10. Quick answers
From the figures on this page.
Wipe schedule
This release records the wipe timetable for Test: what is it?
Test wipes without a fixed interval, so no next wipe can be predicted. A force wipe takes place monthly for every Rust server, with the next on Thursday 5 November at 19:00 UTC. The present world dates from 25 hours.
On Test, what happens on wipe day?
Recent wipes drew an average peak of 4 players. On the latest wipe, 0 hours passed before the crowd peaked. The crowd stayed above half that peak until the next wipe in 50% of recent wipes. In the other cases, half the peak was lost by day 8.
Server record
Is Test up, and how well has it held up?
At the latest check, Test was online. By its own reported uptime, it restarted about 22 hours ago. A total of 95 of 168 hours were up over 7 full days, which is 57% of the time. The first sighting of it by Rust Census was on 27 September 2026.
How well does Test perform?
Average server fps over the last 48 hours was 149, with a low of 113. Buildings, deployables and everything else in the world took the entity count to 121,303. The peak memory use recorded was 4,980 MB. Players feel low fps and a rising entity count as lag.
In which location is Test based?
No region is given by Test. Where a server says it is is what Rust Census shows; where the machine stands is not looked up. 24.113.60.221:28015 is its address.
What version of Rust has been recorded on Test?
The version in use on Test is Rust network protocol 2635 and build 168909 on Windows. To join, your game has to be on the same protocol; Steam handles the update.
Player figures
What are the current player figures for Test?
Test stands at 0 players from 50 slots in this release. This release records a seven-day average of 0 players and a peak of 2. An average of 2 players was recorded at 05:00 UTC, the busiest hour of the last 48.
What position does Test hold in the server rankings?
The rank for Test is #7,688 on seven-day player hours, in the top 35% of ranked servers.
Tags, lists
Which Rust Census filters and lists cover Test?
These Rust Census lists include Test: Modded Rust servers, counted. Under these filters it comes up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days.
What is meant by each tag shown on Test?
These are the tags Test publishes for the game's server browser to read: gmrust (Game mode): The game mode is standard survival as Rust runs it; mp50 (Max players): Slots: 50; ts8 (Group limit): 8 per team, which is the game's default limit; v2635 (Protocol): To connect, your game version must match protocol 2635; cs168909 (Build): The server runs game build 168909; ptrak (Networking): Networking is handled by RakNet, which the game uses by default; $r? (Region code): This server carries no region code; ^z (Modded): Modded: the game is changed by plugins or settings; ^y (Carbon): Carbon, a plugin framework, is installed. The tags also hold the current player count, the queue and the world's creation time, which appear at the top of this page.
Settings and map
Which map has been recorded for Test?
Test runs a procedural map of size 4,500 with seed 62803, generated by the game. The same size and seed produce the same map; RustMaps shows it from this page.
How is Test configured, and what rules does it keep?
No gather rate is recorded for Test in its name. The default applies: groups are capped at 8 players. It runs survival, the standard game: gather, build, raid. Combat between players and raiding are both permitted. The server browser lists it under Modded: plugins or settings alter the game. The plugin count is Carbon. The server runs VAC, Valve's anti-cheat.
Connecting
What steps are needed to join Test?
Enter client.connect 24.113.60.221:28015 in Rust's console, opened with F1. Alternatively, use Launch Rust and join here: Steam opens the game and connects you.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp50,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y
Game
gmrust | Game mode The game mode is standard survival as Rust runs it. |
|---|---|
mp50 | Max players Slots: 50. |
ts8 | Group limit 8 per team, which is the game's default limit. |
v2635 | Protocol To connect, your game version must match protocol 2635. |
cs168909 | Build The server runs game build 168909. |
ptrak | Networking Networking is handled by RakNet, which the game uses by default. |
$r? | Region code This server carries no region code. |
Mods and access
^z | Modded Modded: the game is changed by plugins or settings. |
|---|---|
^y | Carbon Carbon, a plugin framework, is installed. |
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.