Statistical profileOffline
PVE 1 TEST
46.173.129.3:28015 checked 1d ago
Connect to this server
1. Main points
Players now
0/ 100
0% full
7-day average
0
peak 1
Rank
#10,485
top 47%
Last wipe
1d ago
no schedule published
Next wipe
–
no rhythm it keeps
Main points
- The server is offline; at its last check there were 0 players on it, 0% of its 100 slots.
- Over the last seven days it averaged 0 players, with a peak of 1.
- It ranks #10,485 of all ranked servers, the top 47%, on player hours over the last seven days.
- Its current map went up 1d ago.
2. Players
Figure 1: Players on PVE 1 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. 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 47% 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
1 days
between real wipes
On rhythm
0%
of its recent wipes
Wipe-day peak
1
players, last three wipes
Crowd held
67%
else halves by day 2
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 1, 1 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 |
|---|---|---|---|---|
| Tue 27 Oct, 10:53 UTC1d ago | – | – | running | 0 |
| Thu 22 Oct, 15:45 UTC6d ago | 1 | halved by day 2 | 4.8 days | 0 |
| Wed 14 Oct, 18:22 UTC14d ago | 1 | held half | 7.9 days | 0 |
| Tue 13 Oct, 23:06 UTC14d ago | 1 | – | 0.8 days | 0 |
| Mon 12 Oct, 16:33 UTC16d ago | 1 | – | 1.3 days | 0 |
| Fri 2 Oct, 12:21 UTC26d ago | 1 | held half | 10.2 days | 0 |
| Thu 1 Oct, 18:35 UTC FW27d ago | 1 | – | 0.7 days | 0 |
| Thu 1 Oct, 11:45 UTC27d ago | 1 | – | 0.3 days | 0 |
| Wed 30 Sep, 18:58 UTC28d ago | 1 | – | 0.7 days | 1 |
| Mon 28 Sep, 23:25 UTC29d ago | 1 | – | 1.8 days | 1 |
| Mon 28 Sep, 14:47 UTC30d ago | 1 | – | 0.4 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 PVE 1 TEST
Table 2: The world
As the server publishes it
| Map | Procedural Map |
|---|---|
| Size | – |
| Seed | – |
8. Server characteristics
Table 3: Characteristics of PVE 1 TEST
What the server publishes and what was recorded
| Address | 46.173.129.3:28015 |
|---|---|
| Region | – |
| Max players | 100 |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 27 Oct 2026, 10:53 UTC |
| Hostname | – |
| First seen | 13 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 · 157 on average | 205 / 500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 127 on average | 121 / 100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 183 / 225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 90 on average | 126 / 700 |
| RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 19 / 200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 50 / 1000 |
10. Quick answers
From the figures on this page.
Wipe records
On what schedule are wipes carried out on PVE 1 TEST?
No next wipe can be predicted for PVE 1 TEST, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. The present world dates from 32 hours.
On PVE 1 TEST, what happens on wipe day?
Recent wipes drew an average peak of 1 players. The peak of the latest wipe's crowd came 1 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe in 67% of cases. If not, it dropped below half by day 2.
Server details
What does the record show for the uptime and current status of PVE 1 TEST?
The latest count records PVE 1 TEST as offline, last seen 31 hours ago. A total of 36 of 168 hours were up over 7 full days, which is 21% of the time. First recorded by Rust Census on 13 September 2026.
In which location is PVE 1 TEST based?
No region is published by PVE 1 TEST. Rust Census does not look up where the machine stands; it shows where a server says it is. 46.173.129.3:28015 is its address.
On which Rust version does PVE 1 TEST operate?
Rust network protocol 2635 and build 168909 on Windows is the version PVE 1 TEST runs. The same protocol is required for your game to join, and Steam updates it for you.
Player figures
What population has been recorded on PVE 1 TEST?
At this release PVE 1 TEST is offline, having last been seen 31 hours ago. This release records a seven-day average of 0 players and a peak of 1.
How does PVE 1 TEST compare with other servers in the rankings?
For seven-day player hours, PVE 1 TEST is ranked #10,485, placing it in the top 47% of all ranked servers.
Tags, lists
Which Rust Census filters and lists cover PVE 1 TEST?
Included in these Rust Census lists is PVE 1 TEST: Modded Rust servers, counted. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
The tags on PVE 1 TEST: what do they indicate?
Read by the game's server browser, PVE 1 TEST publishes these tags: gmrust (Game mode): Survival play, in the standard Rust format; mp100 (Max players): 100 slots are available; 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): Build 168909 is installed; ptrak (Networking): Networking is handled by RakNet, which the game uses by default; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded: the game is changed by plugins or settings; modded (Modded): Modded: the game is changed by plugins or settings. At the top of this page you will find the tags for current players, queue and world creation time.
Settings and map
What map is listed for PVE 1 TEST?
A procedural map runs on PVE 1 TEST, generated by the game.
How is PVE 1 TEST configured, and what rules does it keep?
The name of PVE 1 TEST carries no gather rate. The default applies: groups are capped at 8 players. It runs survival, the standard game: gather, build, raid. Fighting other players and raiding are allowed. Plugins or settings change the game, and the browser lists it under Modded. Oxide plugins are recorded on it. The server runs VAC, Valve's anti-cheat.
Join details
How can you connect to PVE 1 TEST?
Enter client.connect 46.173.129.3:28015 in the console, opened with F1 after starting Rust; alternatively, Launch Rust on this page opens Rust through Steam and connects you.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp100,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z,modded
Game
gmrust | Game mode Survival play, in the standard Rust format. |
|---|---|
mp100 | Max players 100 slots are available. |
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 Build 168909 is installed. |
ptrak | Networking Networking is handled by RakNet, which the game uses by default. |
$r? | Region code No region code is set. |
Mods and access
^o | Oxide The plugin framework in use is Oxide (uMod). |
|---|---|
^z | Modded Modded: the game is changed by plugins or settings. |
modded | Modded Modded: the game is changed by plugins or settings. |
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.