Statistical profileOnline
Rust solo PVE
85.190.149.48:10900 checked 12m ago
Connect to this server
1. Main points
Players now
0/ 50
0% full
7-day average
0
peak –
Rank
#15,349
top 69%
Last wipe
27d ago
no schedule published
Next wipe
7d 18h
Thu 5 Nov, 19:00 UTC FW
Main points
- There were 0 players on it, 0% of its 50 slots.
- It ranks #15,349 of all ranked servers, the top 69%, on player hours over the last seven days.
- Its current map went up 27d ago; the next wipe is expected Thursday 5 November, 19:00 UTC, the force wipe.
2. Players
Figure 1: Players on Rust solo PVE
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 17 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 69% of all ranked servers. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Patternforce wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 18h. The force wipe · high confidence
Wipe-day peak
0
players, last three wipes
Table 1: Coming wipes
Expected from its own rhythm and the force wipe
| In | Date and time | Kind |
|---|---|---|
| 7d 18h | Thu 5 Nov, 19:00 UTC | Force wipe FW |
| 35d 18h | Thu 3 Dec, 19:00 UTC | Force wipe FW |
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 0, 0 hours in.
Source: Live server queries, Rust Census
6. Wipes
Table 2: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 1 Oct, 18:06 UTC FW27d ago | 0 | – | running | 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 Rust solo PVE
3500 · seed 6738
8. Server characteristics
Table 4: Characteristics of Rust solo PVE
What the server publishes and what was recorded
| Address | 85.190.149.48:10900 |
|---|---|
| Region | – |
| Max players | 50 |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 1 Oct 2026, 18:06 UTC |
| Hostname | – |
| First seen | 13 Sep 2026 |
9. Similar servers
Table 5: 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 · 156 on average | 46 / 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 | 45 / 225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 92 on average | 50 / 700 |
| RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 9 / 200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 6 / 1000 |
10. Quick answers
From the figures on this page.
Wipe records
This release records the wipe timetable for Rust solo PVE: what is it?
A monthly force wipe is the sole occasion on which Rust solo PVE wipes. Every Rust server wipes on Thursday 5 November at 19:00 UTC at the force wipe, which is its next wipe. This world was generated 27 days 5 hours ago.
On Rust solo PVE, what happens on wipe day?
An average of 0 players attended at peak across recent wipes. 0 hours after the latest wipe, the crowd peaked.
About the server
What does the record show for the uptime and current status of Rust solo PVE?
Rust solo PVE is online at the time of this release. The uptime it reports puts the last restart at about 18 hours ago. Of the 168 hours in the last 7 full days, it was up 144 of them, or 86%. The first sighting of it by Rust Census was on 13 September 2026.
How well does Rust solo PVE perform?
The figures for the last 48 hours give an average of 12 server fps and a minimum of 10. The world carried up to 66,636 entities, including buildings, deployables and all else. The peak memory use recorded was 2,069 MB. Players feel low fps and a rising entity count as lag.
In which location is Rust solo PVE based?
No region is given by Rust solo PVE. No lookup of where the machine stands is made by Rust Census; it shows where a server says it is. 85.190.149.48:10900 is its address.
What version of Rust has been recorded on Rust solo PVE?
This release lists Rust solo PVE on Rust network protocol 2635 and build 168909, running on Windows. The same protocol is required for your game to join, and Steam updates it for you.
Population
What population has been recorded on Rust solo PVE?
Rust solo PVE stands at 0 players from 50 slots in this release. This release gives a seven-day average of 0 players.
What position does Rust solo PVE hold in the server rankings?
The rank for Rust solo PVE is #15,349 on seven-day player hours, in the top 69% of ranked servers.
Lists and tags
Which Rust Census filters and lists cover Rust solo PVE?
These Rust Census lists include Rust solo PVE: Modded Rust servers, counted. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
What is meant by each tag shown on Rust solo PVE?
Read by the game's server browser, Rust solo PVE publishes these tags: gmvanilla (Game mode): Survival play in the vanilla format; mp50 (Max players): 50 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): The server runs game build 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): This server is listed as modded, with plugins or settings that change the game. Current players, queue length and world creation time are in the tags as well, and are shown at the top of this page.
Settings and map
Which map is in use on Rust solo PVE?
Size 3,500 and seed 6738: that is the procedural map on Rust solo PVE, generated by the game. Because one size and seed give one map, RustMaps can display it from this page.
What settings and rules have been listed for Rust solo PVE?
No gather rate is recorded for Rust solo PVE in its name. 8 players is the group limit, the game's default. It runs survival, the standard game: gather, build, raid. Raiding and player combat are permitted. The server browser lists it under Modded: plugins or settings alter the game. Plugins on it number Oxide. Anti-cheat is active: VAC, Valve's system, is on.
Connecting
How can you connect to Rust solo PVE?
Enter client.connect 85.190.149.48:10900 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,gmvanilla,cs168909,ts8,^o^z
Game
gmvanilla | Game mode Survival play in the vanilla format. |
|---|---|
mp50 | Max players 50 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 The server runs game build 168909. |
ptrak | Networking The network layer is RakNet, the game's standard. |
$r? | Region code A region code has not been set. |
Mods and access
^o | Oxide The plugin framework in use is Oxide (uMod). |
|---|---|
^z | Modded This server is listed as modded, with plugins or settings that change the game. |
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.