Skip to the page
RUST ANALYTICS
LIVE71,686PLY11,699SRV
QUOTE 85.215.227.142:28016 Online checked 11m ago

Nightly | Solo | Beginner | Vanilla

solo weekly wipes vanillamoddedoxide
Players · last
0/ 100
+024h
0% full
Day range 0 2
7-day avg 0 peak 2
Players · 24 hourshourly average, then now · dashed: 24 hours ago
Launch Rust and join

Key statistics

the figures behind the quote
Players now
0/ 100
0% full
Change · 24h
+0
no reading a day ago
7-day average
0
peak 2
Rank
#8,041
top 36%
Rank · 7d ago
#5,783
2258 places down
Last wipe
3d ago
weekly schedule
Next wipe
3d 13h
Sun 18 Oct, 10:11 UTC
Group limit
solo
players per team
Gather rate
–
no rate in the name
Score
11
player hours, last seven days
Map
3500
Procedural Map · seed 1785397734
First seen
13 Sep 2026
no hostname published

Players

AveragePeak
00.511.5221:0006:0015:0001:0010:0019:00

Hourly average and peak, UTC. Busiest hour of the two days: 2 players.

Server performance

05010015020021:0006:0015:0001:0010:0019:00

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.

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep25 Sep30 Sep4 Oct9 Oct14 Oct

Top 36% of all ranked servers, and #175 of the solo servers (top 80%). Ranked on player hours over the last seven days.

Wipe schedule

fixed weekdays
Next wipeSunday 18 October, 10:11 UTCin 3d 13h

Every Sunday at 10:11 UTC · medium confidence

usual gap
7 days
between real wipes
on rhythm
80%
of its recent wipes
wipe-day peak
3
players, last three wipes
crowd held
25%
else halves by day 1

Coming wipes

  1. 3d 13hSun 18 Oct, 10:11 UTC
  2. 10d 13hSun 25 Oct, 10:11 UTC
  3. 17d 13hSun 1 Nov, 10:11 UTC
  4. 21d 22hThu 5 Nov, 19:00 UTCFW
  5. 24d 13hSun 8 Nov, 10:11 UTC
  6. 31d 13hSun 15 Nov, 10:11 UTC
  7. 38d 13hSun 22 Nov, 10:11 UTC

The first 48 hours of its last wipes

Sun 11 OctSun 4 OctFri 2 Oct
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 11 Oct, 10:11 UTC3d ago 1 – running 0
Sun 4 Oct, 10:11 UTC10d ago 5 halved by day 1 7 days 1
Fri 2 Oct, 10:21 UTC12d ago 2 held half 2 days 0
Sun 27 Sep, 10:11 UTC17d ago 4 halved by day 2 5 days 0
Sun 20 Sep, 10:11 UTC24d ago 7 halved by day 1 7 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
#ServerLastChg 24hPlayers over the last 24 hours24h
1・RUST KILL・XXX|KILL $ CASH|FARM|SHOP|TP|HOME|KITS|PVPVEX10Xgroups of 10+ · weekly · 4 on average3/100+1+28.6%
2[EU] Rustoria.co RTG - Aimtrain | FaceChecks | Arena | 1v1EU · no group limit · 12 on average56/100+35+167.7%
3MINICOPTER / HELICOPTER TRAININGgroups of 8+ · 9 on average18/100+11+148.3%
4PLUKN - US Monument/Oil Rig | Practice, Aimtrain, PVPNA · groups of 8+ · 5 on average11/20+3+36.1%
5[US] Rustoria.co RTG - Aimtrain | FaceChecks | Arena | 1v1NA · no group limit · 3 on average2/100−4−69.2%
6X1000000.RU|HARDPVP|FUN|FPS++|X1000000000000000000000000000000groups of 15+ · 1e+06x · weekly · 146 on average138/360+57+69.7%

Quick answers

from the figures on this page

Map and Rules

How is Nightly | Solo | Beginner | Vanilla configured in terms of rules and settings?

No gather rate appears in the name of Nightly | Solo | Beginner | Vanilla. No teams: solo only. It runs combat training, practice for aim and PvP, with loot provided. The server browser lists it as Modded: plugins or settings change the game. Plugin count: Oxide. Its self-description is vanilla: facepunch's build, untouched: no rate changes, no kits, no rule changes. The server has VAC, Valve's anti-cheat, switched on.

What is the current map on Nightly | Solo | Beginner | Vanilla?

A procedural map of size 3,500 with seed 1785397734 runs on Nightly | Solo | Beginner | Vanilla, created by the game. Because size and seed determine the map, RustMaps offers a view of it from this page.

Population

What position does Nightly | Solo | Beginner | Vanilla hold in the server rankings?

In the top 36% of all ranked servers, Nightly | Solo | Beginner | Vanilla is #8,041 on player hours over the last seven days. In the solo group, it ranks #175.

How full is Nightly | Solo | Beginner | Vanilla?

On Nightly | Solo | Beginner | Vanilla, 0 players are in now, out of 100 slots. The seven-day average is 0 players, with a peak of 2. At 18:00 UTC in the last 48 hours, it averaged 1 players, the busiest hour.

Wipe Cycle

What can you expect on wipe day for Nightly | Solo | Beginner | Vanilla?

The average peak across its recent wipes is 3 players. On the latest wipe, 1 hours after the wipe, the crowd peaked. Half the peak was held until the next wipe in 25% of its recent wipes. Below half by day 1 is where the crowd fell when it did not hold.

How often does Nightly | Solo | Beginner | Vanilla wipe?

Nightly | Solo | Beginner | Vanilla wipes on this rhythm: every Sunday at 10:11 UTC. The date of its next wipe is Sunday 18 October at 10:11 UTC. This world has been running for 3 days 10 hours. Its tags state a wipe every week.

Server Overview

What is the server location for Nightly | Solo | Beginner | Vanilla?

No region is published by Nightly | Solo | Beginner | Vanilla. The location shown by Rust Analytics is the one a server states; it does not verify the machine's position. You can reach it at 85.215.227.142:28016.

Is Nightly | Solo | Beginner | Vanilla performing well?

Average server fps for the last 48 hours is 71; the floor was 24. At its peak it held 76,494 entities: buildings, deployables and the rest of the world. Up to 2,243 MB of memory was used. Low fps and growing entities are the source of felt lag.

Nightly | Solo | Beginner | Vanilla is on which Rust version?

Rust network protocol 2634 and build 167781 on Windows is what Nightly | Solo | Beginner | Vanilla runs. Joining requires the same protocol on your game, which Steam updates.

Is Nightly | Solo | Beginner | Vanilla up, and how consistent is its uptime?

The server is live: Nightly | Solo | Beginner | Vanilla is online. The reported uptime puts its last restart at about 8 hours ago. 7 full days have passed with 100% uptime, 168 of 168 hours. First sighting by Rust Analytics: 13 September 2026.

Tags & Filters

What is the meaning of the tags on Nightly | Solo | Beginner | Vanilla?

These tags are published by Nightly | Solo | Beginner | Vanilla and read by the game's server browser: gmrust (Game mode): Rust's standard survival mode; mp100 (Max players): Capacity: 100 slots; ts1 (Group limit): Teams take no more than 1; v2634 (Protocol): Your game must run protocol 2634 to connect; cs167781 (Build): It runs build 167781; ptrak (Networking): Runs on RakNet, Rust's default network layer; $r? (Region code): No region code has been set; ^w (Weekly): Wipes land every week; ^v (Vanilla): Facepunch's build, untouched: no rate changes, no kits, no rule changes; ^d (Combat training): A practice server for aim and PvP, with loot provided; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Categorised as Modded: plugins or settings alter gameplay. The tags also carry its current players, queue and world creation time; this page shows them at the top.

Where does Nightly | Solo | Beginner | Vanilla show up in Rust Analytics lists and filters?

These Rust Analytics lists include Nightly | Solo | Beginner | Vanilla: Rust servers for new players, Modded Rust servers, Rust aim training servers and Solo Rust servers. These filters bring it up on the server list: Type: Vanilla and Modded; Server tag: Weekly ^w, Vanilla ^v, Combat training ^d, Modded ^z and Oxide ^o; Group limit: Solo; Wipe schedule: Weekly; Last wipe: In the last week.

Connection

What is the process to join Nightly | Solo | Beginner | Vanilla?

Type client.connect 85.215.227.142:28016 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you.

Server tags

what each one means

Published as mp100,ptrak,$r?,v2634,^w,^v,^d,gmrust,cs167781,ts1,^o^z

Game

gmrust
Game mode Rust's standard survival mode.
mp100
Max players Capacity: 100 slots.
ts1
Group limit Teams take no more than 1.
v2634
Protocol Your game must run protocol 2634 to connect.
cs167781
Build It runs build 167781.
ptrak
Networking Runs on RakNet, Rust's default network layer.
$r?
Region code No region code has been set.

Wipe schedule

^w
Weekly Wipes land every week.

Difficulty

^v
Vanilla Facepunch's build, untouched: no rate changes, no kits, no rule changes.

Gameplay

^d
Combat training A practice server for aim and PvP, with loot provided.

Mods and access

^o
Oxide Oxide (uMod) provides the plugin framework here.
^z
Modded Categorised as Modded: plugins or settings alter gameplay.

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.