10/15 WEEKLY SOLO/DUO/TRIO Pepega Vanilla
Online 64.74.161.167:28221 checked 8m ago
Li2Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Li3Server performance
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.
Li4Rank
daily · 1 is bestTop 29% of all ranked servers, and #395 of the trio servers (top 63%). Ranked on player hours over the last seven days.
Bx1Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 1 hours in.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 22 Oct, 12:26 UTC6d ago | 2° | – | running | 0 |
| Fri 16 Oct, 16:28 UTC12d ago | 1° | held half | 5.8 days | 0 |
| Thu 8 Oct, 21:06 UTC20d ago | 1° | halved by day 6 | 7.8 days | 0 |
| Sat 3 Oct, 13:03 UTC25d ago | 3° | halved by day 2 | 5.3 days | 0 |
| Thu 24 Sep, 16:46 UTC34d ago | 2° | halved by day 4 | 8.8 days | 0 |
| Thu 17 Sep, 20:40 UTC41d ago | 2° | halved by day 3 | 6.8 days | 0 |
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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe day
What does wipe day look like on 10/15 WEEKLY SOLO/DUO/TRIO Pepega Vanilla?
Its recent wipes drew an average peak of 1 players. The crowd on the latest wipe reached its peak 1 hours in. The crowd stayed above half that peak until the next wipe in 20% of its recent wipes. It fell below half by day 3.5 when it did not hold.
What is the wipe schedule on 10/15 WEEKLY SOLO/DUO/TRIO Pepega Vanilla?
No next wipe can be predicted: 10/15 WEEKLY SOLO/DUO/TRIO Pepega Vanilla wipes when it chooses, at irregular times. Thursday 5 November at 19:00 UTC is the next monthly force wipe, when every Rust server wipes. 6 days 17 hours ago the server made the world it is on now.
Population
How busy is 10/15 WEEKLY SOLO/DUO/TRIO Pepega Vanilla?
The current population of 10/15 WEEKLY SOLO/DUO/TRIO Pepega Vanilla is 0, against 100 slots. Averaged over the past week: 0 players, peaking at 2. Look at 01:00 UTC for the last 48 hours: that hour averaged 1 players.
How does 10/15 WEEKLY SOLO/DUO/TRIO Pepega Vanilla rank against other Rust servers?
The top 29% of ranked servers includes 10/15 WEEKLY SOLO/DUO/TRIO Pepega Vanilla, at #6,491 for player hours over the last seven days. Ranked against other trio servers, it comes in at #395.
Rules and settings
Which map does 10/15 WEEKLY SOLO/DUO/TRIO Pepega Vanilla run?
10/15 WEEKLY SOLO/DUO/TRIO Pepega Vanilla runs a procedural map of size 4,500 with seed 753894, generated by the game. From this page you can view the map on RustMaps, since the same size and seed give the same map.
What are the rules and settings on 10/15 WEEKLY SOLO/DUO/TRIO Pepega Vanilla?
No gather rate appears in the name 10/15 WEEKLY SOLO/DUO/TRIO Pepega Vanilla. 3 players is the maximum group size (trio). The server runs survival, standard play: gathering, building and raiding. You can fight other players and raid their bases. You will find it under Community in the server browser; it is a community server. Plugin count: Oxide. The server has VAC, Valve's anti-cheat, turned on.
Server details
Which version of Rust does 10/15 WEEKLY SOLO/DUO/TRIO Pepega Vanilla run?
Rust network protocol 2635 and build 168909 on Windows is what 10/15 WEEKLY SOLO/DUO/TRIO Pepega Vanilla runs. Steam updates your game for you, and the protocol has to match for you to join.
Is 10/15 WEEKLY SOLO/DUO/TRIO Pepega Vanilla online, and how reliable is it?
Online now: 10/15 WEEKLY SOLO/DUO/TRIO Pepega Vanilla. The uptime it reports puts the last restart at about 22 hours ago. 167 of 168 hours up over the last 7 full days, which is 99%. The first record of it on Rust Heatmap is 13 September 2026.
Where is 10/15 WEEKLY SOLO/DUO/TRIO Pepega Vanilla located?
No region is published by 10/15 WEEKLY SOLO/DUO/TRIO Pepega Vanilla. What Rust Heatmap shows is where a server says it is. Where the machine stands is not looked up. To connect, use 64.74.161.167:28221.
Does 10/15 WEEKLY SOLO/DUO/TRIO Pepega Vanilla run smoothly?
The last 48 hours brought an average of 73 server fps and a floor of 40. Entities peaked at 117,087, counting buildings, deployables and all the rest of the world. Memory use reached 3,618 MB at most. What players call lag is low fps together with a growing entity count.
Tags
Which Rust Heatmap lists and filters include 10/15 WEEKLY SOLO/DUO/TRIO Pepega Vanilla?
The Rust Heatmap lists that 10/15 WEEKLY SOLO/DUO/TRIO Pepega Vanilla fits are: Best Rust community servers and Trio Rust servers. These are the filters that return it on the list: Type: Community (not modded, not official) and Plugins, not modded; Server tag: Oxide ^o; Group limit: Trio; Last wipe: In the last week.
What do the server tags on 10/15 WEEKLY SOLO/DUO/TRIO Pepega Vanilla mean?
gmrust (Game mode): Survival in the standard Rust form; mp100 (Max players): This server has 100 slots; ts3 (Group limit): The team limit is 3; v2635 (Protocol): To join, run the same version: game protocol 2635; cs168909 (Build): This build is 168909; ptrak (Networking): Standard game networking here, which is RakNet; $r? (Region code): The region code is blank; ^o (Oxide): Plugins run through Oxide (uMod) are the tags 10/15 WEEKLY SOLO/DUO/TRIO Pepega Vanilla publishes, and the server browser reads them. Players now, the queue and the world's creation time sit in the tags as well and appear at the top of this page.
Connect
How do I join 10/15 WEEKLY SOLO/DUO/TRIO Pepega Vanilla?
Enter client.connect 64.74.161.167:28221 in the console, opened with F1 in Rust. Or use Launch Rust here, which opens the game through Steam and connects you.