Loker
Offline 82.131.109.23:28015 checked 41d 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- 97/500
- 125/100
- 99/225
- 41/700
- 5/200
- 16/1000
Quick answers
from the figures on this pageWipe timing
What wipe timing does Loker follow?
The rhythm of Loker's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 41 days 1 hours ago the current world was made.
Lists and filters
Which tags does Loker carry, and what do they mean?
Tags published by Loker, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp500 (Max players): The server holds 500 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163794 (Build): Game build reading: 163794; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Plugins or settings make this a modded server. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does Loker appear in Rust Metrics lists and filters?
On Rust Metrics, Loker sits in these lists: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Population
What position does Loker hold among Rust servers?
Player hours over seven days put Loker at #13,339, in the top – of all ranked servers.
What is the population on Loker?
Status for Loker: offline. Last seen 41 days ago.
Server
Where does Loker sit?
No region tag on Loker. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 82.131.109.23:28015.
What Rust version is Loker on?
Rust network protocol 2633 and build 163794 on Windows is the build Loker runs. Check: protocol. To join, your game must match; Steam handles the update.
What is the uptime on Loker, and is it online?
Reading: offline. Loker last answered 41 days ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 17 September 2026, recorded by Rust Metrics.
Map and rules
What settings and rules apply on Loker?
No gather rate appears in the name: Loker. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.
What map is Loker on?
Procedural map on Loker, made by the game's generator.
Connection
How can you get onto Loker?
To join: start Rust, press F1 and type client.connect 82.131.109.23:28015. Or press Launch Rust here and Steam opens the game and connects you.