SHARP.NET ( Solo/Duo )-2x All ( Chilled ) Small Map - WEEKLY
Online 203.16.163.142:27267 checked 9m ago
- Wipedunder 6 hours
- Fillingthe first day
- Peakthe first days
- Settledlater on
- Due againnext wipe close
Players, performance and rank
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server 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.
Rank
daily · 1 is bestTop 68% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Sunday 1 November, 15:36 UTC · 15:36 UK, in 2d 20h.
Its weekly schedule tag · low confidenceComing wipes
- 2d 20hSun 1 Nov, 15:36 UTC15:36 UK
- 6d 23hThu 5 Nov, 19:00 UTC19:00 UKFW
- 9d 20hSun 8 Nov, 15:36 UTC15:36 UK
- 16d 20hSun 15 Nov, 15:36 UTC15:36 UK
- 23d 20hSun 22 Nov, 15:36 UTC15:36 UK
- 30d 20hSun 29 Nov, 15:36 UTC15:36 UK
- 34d 23hThu 3 Dec, 19:00 UTC19:00 UKFW
- 37d 20hSun 6 Dec, 15:36 UTC15:36 UK
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 5 hours in.
Wipes
every wipe as a delivery, newest first-
Sun 1 Nov, 15:36 UTC15:36 UK · in 2d 20hNext wipe expected · its weekly schedule tag
-
Sun 11 Oct, 15:36 UTC 16:36 UK · 18d agoWipe delivered
- Peak
- 2
- Crowd
- –
- Lasted
- running
- Players before
- 1
-
Fri 2 Oct, 09:41 UTC 10:41 UK · 27d agoWipe delivered
- Peak
- 2
- Crowd
- halved by day 3
- Lasted
- 9.2 days
- Players before
- 0
-
Fri 25 Sep, 19:43 UTC 20:43 UK · 33d agoWipe delivered
- Peak
- 4
- Crowd
- halved by day 2
- Lasted
- 6.6 days
- Players before
- 0
-
Sun 20 Sep, 09:47 UTC 10:47 UK · 39d agoWipe delivered
- Peak
- 1
- Crowd
- halved by day 3
- Lasted
- 5.4 days
- Players before
- 0
-
Sat 19 Sep, 20:28 UTC 21:28 UK · 39d agoWipe delivered
- Peak
- 1
- Crowd
- –
- Lasted
- 0.6 days
- Players before
- 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.
Similar servers
The same kind of game, then region, group limit, rate and wipes.
- Magic Rust #18 — Vanilla 2x | Baйп 28.10 730 / 900
- MIRAGE RUST | SUNDAY 2x | VANILLA+ | Wipe 25.10 120 / 1000
- Magic Rust #14 — Modded 2x (No limit) | Pyccкий 176 / 260
- MIRAGE RUST | MONDAY 2x | VANILLA+ | Wipe 26.10 247 / 1900
- РОССИЯ X2 / ДЛЯ НОВИЧКОВ / THIS IS RUST! 65 / 100
- VANILLA x2 | GGRust #4 | Для нoвичкoв 2x 15 / 100
Quick answers
From the figures on this page.
Player activity
Where does SHARP.NET ( Solo/Duo )-2x All ( Chilled ) Small Map - WEEKLY place among Rust servers?
Over the past seven days, SHARP.NET ( Solo/Duo )-2x All ( Chilled ) Small Map - WEEKLY has climbed to #15,141 for player hours, putting it in the top 68% of all ranked servers.
How many players are on SHARP.NET ( Solo/Duo )-2x All ( Chilled ) Small Map - WEEKLY right now?
Checking now: 0 players on 40 slots at SHARP.NET ( Solo/Duo )-2x All ( Chilled ) Small Map - WEEKLY. The seven-day figures show an average of 0 players and a peak of 1. The busiest hour over the last 48 hours was 10:00 UTC, averaging 0 players.
Map and rules
On what map does SHARP.NET ( Solo/Duo )-2x All ( Chilled ) Small Map - WEEKLY take place?
Size 2,000 and seed 50000 define the procedural map SHARP.NET ( Solo/Duo )-2x All ( Chilled ) Small Map - WEEKLY runs, generated by the game. Size and seed match means the map matches, so you can view it on RustMaps from this page.
What are the rules on SHARP.NET ( Solo/Duo )-2x All ( Chilled ) Small Map - WEEKLY, and what settings does it run?
You get 2x gather on SHARP.NET ( Solo/Duo )-2x All ( Chilled ) Small Map - WEEKLY, going by its name. Up to 8 players can join a group, the default for the game. You get survival here, the usual game: build, gather, raid. You can raid and fight other players. The server browser lists it as Modded, because plugins or settings alter the game. The plugins run on Oxide. The vanilla label is one it applies to itself: no altered rates, kits or rules: the game as shipped by Facepunch. VAC, the anti-cheat from Valve, is active.
Operator and location
What is the location of SHARP.NET ( Solo/Duo )-2x All ( Chilled ) Small Map - WEEKLY?
You will find no region published by SHARP.NET ( Solo/Duo )-2x All ( Chilled ) Small Map - WEEKLY. The location shown on Rust Wipe Tracker is the one a server gives; where the machine stands is not looked up. The address to connect to is 203.16.163.142:27267.
How smoothly does SHARP.NET ( Solo/Duo )-2x All ( Chilled ) Small Map - WEEKLY run?
Server fps over the last 48 hours averaged 227; the lowest was 185. The world held as many as 17,519 entities: buildings, deployables and the rest. The highest memory reading was 2,845 MB. What players call lag is the mix of low fps and an entity count that keeps climbing.
How reliable is SHARP.NET ( Solo/Duo )-2x All ( Chilled ) Small Map - WEEKLY, and is it currently online?
Right now, SHARP.NET ( Solo/Duo )-2x All ( Chilled ) Small Map - WEEKLY is online. Its reported uptime suggests a restart roughly 4 hours ago. It was up 167 of 168 hours over the last 7 full days, 99% of the time. The first sighting of it by Rust Wipe Tracker came on 17 September 2026.
What Rust version is SHARP.NET ( Solo/Duo )-2x All ( Chilled ) Small Map - WEEKLY using?
On Linux, SHARP.NET ( Solo/Duo )-2x All ( Chilled ) Small Map - WEEKLY runs Rust network protocol 2635 and build 168909. The same protocol is required to join, and Steam takes care of updating it.
Wipe times
How does SHARP.NET ( Solo/Duo )-2x All ( Chilled ) Small Map - WEEKLY handle its wipe days?
The average busiest point of its recent wipes was 3 players. After 5 hours the latest wipe's crowd hit its peak. Until the next wipe, the crowd stayed over half the peak in 0% of recent cases. By day 3 it had fallen below half where the crowd did not hold.
How often does SHARP.NET ( Solo/Duo )-2x All ( Chilled ) Small Map - WEEKLY wipe, and at what times?
The prediction is taken from its tag, as SHARP.NET ( Solo/Duo )-2x All ( Chilled ) Small Map - WEEKLY has too few wipes on record to confirm the schedule. Due on Sunday 1 November at 15:36 UTC: its next wipe. You are playing a world created 18 days 3 hours. Its tags give a wipe schedule of once a week.
Tags and listings
Where does SHARP.NET ( Solo/Duo )-2x All ( Chilled ) Small Map - WEEKLY appear across the Rust Wipe Tracker lists and filters?
The Rust Wipe Tracker lists that include SHARP.NET ( Solo/Duo )-2x All ( Chilled ) Small Map - WEEKLY are: Rust servers with a 2x gather rate and Modded Rust servers. These are the filters that bring it up on the server list: Type: Vanilla and Modded; Server tag: Weekly ^w, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Gather rate: 2x.
How should you read the tags on SHARP.NET ( Solo/Duo )-2x All ( Chilled ) Small Map - WEEKLY?
Read off the game's server browser, the tags for SHARP.NET ( Solo/Duo )-2x All ( Chilled ) Small Map - WEEKLY are: gmrust (Game mode): Survival in standard Rust; mp40 (Max players): It holds 40 slots; ts8 (Group limit): Team limit: 8, the standard default; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet handles networking, as standard for the game; $r? (Region code): The region code is unset; ^w (Weekly): It wipes weekly; ^v (Vanilla): No altered rates, kits or rules: the game as shipped by Facepunch; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. Players now, the queue and the world's creation time sit at the top of this page and come from the tags as well.
Connecting
What steps do you take to join SHARP.NET ( Solo/Duo )-2x All ( Chilled ) Small Map - WEEKLY?
Use Launch Rust on this page to join, which opens Rust through Steam and connects you, or start Rust, press F1 and enter client.connect 203.16.163.142:27267.