RUST METRICSFlight deck · live data
Data live Servers11,747 Players54,200 Populated3,368 Fresh wipes 3 h130 Scan5 min
‹ All servers78.56.33.140:28015
Offline Full Queue Fresh wipe Wipe due No query

Biciukas server

Offline 78.56.33.140:28015 checked 41d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 1 /1

Players now

100% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#13,250no region published
Last wipe44d agono schedule published
Next wipe–too few wipes seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep21 Sep22 Sep23 Sep24 Sep
PLAN

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 23 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 14 Sep, 19:26 UTC44d ago 1 – running 0

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

What should you expect from wipe day on Biciukas server?

At their busiest, its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 23 hours in.

What wipe timing does Biciukas server follow?

Its rhythm cannot be told from the wipes of Biciukas server on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 44 days 4 hours ago the current world was made.

Lists and filters

Which tags does Biciukas server carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): 1 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163794 (Build): Game build reading: 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty from Biciukas server. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does Biciukas server appear in Rust Metrics lists and filters?

These Rust Metrics lists carry Biciukas server: 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.

Occupancy

What position does Biciukas server hold among Rust servers?

Player hours over seven days put Biciukas server at #13,250, in the top – of all ranked servers.

How full does Biciukas server get?

Biciukas server is not responding; status offline, last seen 41 days 2 hours ago.

Operator and location

Where does Biciukas server sit?

No region comes from Biciukas server. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 78.56.33.140:28015.

What Rust version is Biciukas server on?

Rust network protocol 2633 and build 163794 on Windows is the build Biciukas server runs. Matching protocol is required to join. Let Steam update your game.

Is Biciukas server up, and how often does it stay up?

Check: connection. Biciukas server is offline at this moment. Last contact was 41 days 2 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

How is Biciukas server configured, and what rules are in force?

Check: gather rate. The name Biciukas server does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

What map is Biciukas server on?

Procedural map on Biciukas server, made by the game's generator.

Connection

How can you get onto Biciukas server?

Press F1 in Rust and enter client.connect 78.56.33.140:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2633,gmrust,cs163794,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players 1 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Protocol 2633: join only on the same game version.
cs163794
Build Game build reading: 163794.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

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.