Solo/Duo Biweekly #3 test
Key statistics
the figures behind the quote- Players now
- 0/ 215 0% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #16,811 top 70%
- Rank · 7d ago
- – not ranked a week ago
- Last wipe
- 8d ago no schedule published
- Next wipe
- – no wipe seen yet
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 0 player hours, last seven days
- Map
- – Wiped 25 minutes ago
- First seen
- 3 Nov 2026 no hostname published
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 5 Nov, 19:00 UTC FW6d ago | – | – | running | – |
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| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | STEEL RUST /ДЛЯ НОВИЧКОВ /EU Main 11.11EU · groups of 24+ · monthly · 140 on average | 54/100 | ▼−373−87.4% | |
| 2 | 666 RUST /ДЛЯ НОВИЧКОВ /ПИТЕРСКИЙ 11.11EU · groups of 16+ · monthly · 136 on average | 49/750 | ▼−224−82.0% | |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЙСКИЙ 11.11EU · groups of 16+ · monthly · 129 on average | 199/1000 | ▼−126−38.8% | |
| 4 | МИНИ-КАРТА 2Х | STORM | FPS+ 11.11EU · groups of 8+ · weekly · 127 on average | 132/100 | ▲+3+2.4% | |
| 5 | ShockRust | Blue | NoLimitno group limit · 121 on average | 145/400 | ▼−49−25.4% | |
| 6 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 12.11EU · groups of 16+ · monthly · 118 on average | 367/1000 | ▲+317+640.2% |
Quick answers
from the figures on this pageServer Rules
What settings and rules are in place on Solo/Duo Biweekly #3 test?
No gather rate is given in the name of Solo/Duo Biweekly #3 test. Up to 8 players per group, which is the game's default. It runs survival, gather, build and raid in the standard game. PvP and raiding are enabled. The server browser lists it as Modded: plugins or settings change the game. Oxide plugins are running. The server has VAC, Valve's anti-cheat, switched on.
Activity
Where does Solo/Duo Biweekly #3 test sit in the rankings?
In the top 70% of all ranked servers, Solo/Duo Biweekly #3 test is #16,811 on player hours over the last seven days.
What is the population on Solo/Duo Biweekly #3 test?
Right now, Solo/Duo Biweekly #3 test is offline; the last sighting was 8 days 20 hours ago.
Wipe Frequency
When does Solo/Duo Biweekly #3 test schedule its wipes?
The record holds too few of Solo/Duo Biweekly #3 test's wipes to establish its rhythm. The monthly force wipe takes every Rust server. Next: Thursday 3 December at 19:00 UTC. This world has been running for 8 days 21 hours.
Server Details
What is the location of Solo/Duo Biweekly #3 test?
No region is published by Solo/Duo Biweekly #3 test. Where a server says it is, Rust Analytics shows; where the machine stands, it does not look up. 94.249.246.84:28015 is its address.
Solo/Duo Biweekly #3 test runs which version of Rust?
Rust network protocol 2635 and build 168909 on Linux is what Solo/Duo Biweekly #3 test runs. The protocol has to match for you to join, and Steam applies that update.
What is the uptime and reliability of Solo/Duo Biweekly #3 test?
No response from Solo/Duo Biweekly #3 test. It was last seen 8 days 20 hours ago. The last 7 full days give 0% uptime, 0 hours on out of 168. 3 November 2026 is when Rust Analytics first saw it.
Tags and Rankings
What is the meaning of the tags on Solo/Duo Biweekly #3 test?
The game's server browser reads gmrust (Game mode): Rust's standard survival mode; mp215 (Max players): Capacity: 215 slots; ts8 (Group limit): Team size stays at the game default of 8; v2635 (Protocol): To join, your game needs protocol 2635; cs168909 (Build): Game build: 168909; ptrak (Networking): Runs on RakNet, Rust's default network layer; $r? (Region code): The region code is absent; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): Categorised as Modded: plugins or settings alter gameplay, which Solo/Duo Biweekly #3 test publishes. The top of this page and the tags both show its players now, its queue and when its world was made.
Solo/Duo Biweekly #3 test appears in which of the lists and filters on Rust Analytics?
These Rust Analytics lists include Solo/Duo Biweekly #3 test: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Connection
What is the process to join Solo/Duo Biweekly #3 test?
Type client.connect 94.249.246.84:28015 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 meansPublished as mp215,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
mp215
ts8
v2635
cs168909
ptrak
$r?
Mods and access
^o
^z
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.