SoloWibe
Offline 168.222.197.241:28015 checked 46d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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 bestWipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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- 46/250
- 75/200
- 242/300
- 11/100
- 294/375
- 256/300
Quick answers
from the figures on this pageReset cycle
What wipe timing does SoloWibe follow?
To tell the rhythm of SoloWibe, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 46 days 16 hours ago the current world was made.
Tags
How should you read the tags on SoloWibe?
Tags published by SoloWibe, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp2 (Max players): Slots: 2; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163794 (Build): Build 163794; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show SoloWibe?
These Rust Metrics lists carry SoloWibe: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Population
What player count does SoloWibe carry?
Reading for SoloWibe: offline at this moment; last seen 46 days 12 hours ago.
Server
What location is SoloWibe hosted in?
No region comes from SoloWibe. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 168.222.197.241:28015.
What Rust version is SoloWibe on?
Rust network protocol 2633 and build 163794 on Windows is the build SoloWibe runs. Check: protocol. To join, your game must match; Steam handles the update.
How reliable is SoloWibe, and is it online now?
SoloWibe reports offline. The last reading came 46 days 12 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 13 September 2026.
Rules and settings
What settings and rules apply on SoloWibe?
Check: gather rate. The name SoloWibe does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.
What map is SoloWibe on?
The game generates a procedural map for SoloWibe.
Join
How can you get onto SoloWibe?
Press F1 in Rust and enter client.connect 168.222.197.241:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.