Offline168.222.197.241:28015checked 31d ago
SoloWibe
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 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 wipesQuick answers
from the figures on this pageSettings and map
What configuration does SoloWibe use?
A gather rate is absent from the name of SoloWibe. The group limit is the game's default of 8 players. survival is the game mode, gather, build, raid: the standard game. Fighting and raiding between players is allowed. It appears in the Community section of the server browser as a community server. Anti-cheat VAC from Valve is on.
What map is used on SoloWibe?
A procedural map, generated by the game, runs on SoloWibe.
Tags, lists and filters
Where can SoloWibe be found in Rust Player Count lists and filters?
These Rust Player Count lists include SoloWibe: Best Rust PvE servers. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
What information do the tags on SoloWibe convey?
For the game's server browser, SoloWibe publishes: gmrust (Game mode): The usual Rust survival experience; mp2 (Max players): The server has 2 slots; ts8 (Group limit): Teams max out at 8, the standard game limit; v2633 (Protocol): To join, your game must match protocol 2633; cs163794 (Build): The game build is 163794; ptrak (Networking): The network layer is RakNet, Rust's standard one; $r? (Region code): The region code field is empty. You will also find its current players, its queue and its world creation time in the tags, displayed at the top of this page.
Player count
What is the player count on SoloWibe?
SoloWibe is offline at the moment; the last time it was seen was 31 days 23 hours ago.
Server information
What is the uptime and reliability of SoloWibe?
SoloWibe is down at the moment and was last seen 31 days 23 hours ago. In the last 7 full days, it was up for 0 of 168 hours, which is 0% uptime. Rust Player Count recorded it for the first time on 13 September 2026.
What is the Rust version for SoloWibe?
Windows hosts SoloWibe, which runs Rust network protocol 2633 and build 163794. The protocol has to match for you to join, but Steam updates it without any action from you.
What region does SoloWibe serve?
There is no region published by SoloWibe. Rust Player Count displays the location a server claims, not the physical location of the machine. It is located at 168.222.197.241:28015.
Wipe days
When does SoloWibe wipe?
The rhythm of wipes on SoloWibe cannot be told yet, since too few are on record. Next on Thursday 5 November at 19:00 UTC, the monthly force wipe applies to all Rust servers. It has been running its current world for 32 days 4 hours.
Connect to the server
What steps are needed to join SoloWibe?
Open the Rust console with F1, then type client.connect 168.222.197.241:28015. Alternatively, fit into the server through the Launch Rust button on this page; that starts Rust via Steam and joins you.
Server tags
what each one meansPublished as mp2,ptrak,$r?,v2633,gmrust,cs163794,ts8
Game
gmrust
mp2
ts8
v2633
cs163794
ptrak
$r?
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.