Station XX-14092 · no signal
GlukozaTEST
Offline 104.28.198.245:28015 checked 2d ago
- Players now
- 1/ 15
- 7% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 1
- peak 1
- Rank
- #14,092
- top 63%
- Last wipe
- 2d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 15 slots
- Motion · 24 h
- M –not enough readings
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 63% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 18.2 daysbetween real wipes
- wipe-day peak
- 1players, last three wipes
- crowd held
- 100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 11 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Sun 25 Oct, 19:36 UTC2d ago | M0.0■steady | 1 | – | – | running | 1 |
| Wed 7 Oct, 15:00 UTC20d ago | M0.0■steady | 1 | – | held half | 18.2 days | 1 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 pageServer rules
Which settings and rules apply on GlukozaTEST?
You will find no gather rate in the name of GlukozaTEST. The group limit is 8 players, the game's default. survival is the game mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.
Live population
How many players are recorded on GlukozaTEST right now?
No players are recorded on GlukozaTEST at this moment; it is offline, and the last sighting was 2 days 4 hours ago. Across seven days this server recorded an average of 1 players and a peak of 1.
How does GlukozaTEST rank against other Rust servers?
The last seven days of player hours place GlukozaTEST at #14,092, in the top 63% of all ranked servers.
Server details
How reliably does GlukozaTEST stay online?
GlukozaTEST is down at the moment; the last recorded contact was 2 days 4 hours ago. It was up 1% of the time across the last 7 full days: 1 of 168 hours. 7 October 2026 is when Rust Server Trends first recorded it.
Which region does GlukozaTEST run from?
A region is not published by GlukozaTEST. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 104.28.198.245:28015.
Which Rust version is GlukozaTEST running?
On Windows, GlukozaTEST runs Rust network protocol 2635 and build 168909. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe day
What does wipe day look like on GlukozaTEST?
1 players, on average, was the busiest crowd at its recent wipes. 11 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 100% of its recent wipes.
How often does GlukozaTEST wipe, and on which days?
The rhythm of GlukozaTEST cannot yet be told: too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 2 days 15 hours is how long the current world has been running.
Server tags
What do the server tags on GlukozaTEST mean?
Tags published by GlukozaTEST and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp15 (Max players): 15 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): Game build: 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does GlukozaTEST appear?
These Rust Server Trends lists include GlukozaTEST: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
Join the server
How do you connect to GlukozaTEST?
To join, enter client.connect 104.28.198.245:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.