Station XX-13830 · no signal
llamas_build
Offline 76.104.183.243:28015 checked 25d ago
- Players now
- 1/ 4
- 25% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #13,830
- top 60%
- Last wipe
- 26d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 4 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 60% 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
- 15 daysbetween real wipes
- wipe-day peak
- 1players, last three wipes
- crowd held
- 0%else halves by day 9
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 1 Oct, 18:57 UTC FW26d ago | M0.0▲rising | 1 | – | running | 0 | |
| Wed 16 Sep, 19:40 UTC41d ago | M0.0■steady | 1 | halved by day 9 | 15 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 pageMap and rules
Which settings and rules apply on llamas_build?
The name of llamas_build gives no gather rate. At the game's default, groups can have up to 8 players. In survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Carbon. VAC, Valve's anti-cheat, is switched on.
Population
What is the current population on llamas_build?
No players are recorded on llamas_build at this moment; it is offline, and the last sighting was 25 days 18 hours ago.
How does llamas_build rank against other Rust servers?
On player hours for the past week, llamas_build sits at #13,830, which puts it inside the top 60% of every ranked server.
Operator and location
How reliably does llamas_build stay online?
As recorded now, llamas_build is not reachable, the last contact having been 25 days 18 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 13 September 2026 it was recorded for the first time by Rust Server Trends.
Which region does llamas_build run from?
Nothing about a region comes from llamas_build. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 76.104.183.243:28015.
Which Rust version is llamas_build running?
On Windows, llamas_build runs Rust network protocol 2634 and build 166494. 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 llamas_build?
On average, the busiest point of its recent wipes drew 1 players. 0 hours after the latest wipe, the crowd peaked. Until the next wipe the crowd remained above half that peak in 0% of its recent wipes. By day 9 it fell below half in the wipes where it didn't hold.
How often does llamas_build wipe, and on which days?
Too few wipes of llamas_build are on record yet to show its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. 26 days 3 hours is how long the current world has been running.
Server tags
What do the server tags on llamas_build mean?
Tags published by llamas_build and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp4 (Max players): The server has 4 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166494 (Build): The game build is 166494; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): A plugin framework, Carbon, runs here. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does llamas_build appear?
These Rust Server Trends lists include llamas_build: Modded Rust servers, tracked live and Rust build and creative servers, live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How to join
How do you connect to llamas_build?
You can connect by pressing F1 in Rust and typing client.connect 76.104.183.243:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects 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.