Working its way up from the back of the class: #15,929 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
100/ 100
A+
Holds its players well after a wipe: 100% of wipes kept half their crowd.
Momentumrank now against a week ago
37/ 100
F
Slipped a little: down 4,299 places this week. Nothing a good wipe can't fix.
A fair term, with more to come.
Strongest in wipe hold (A+); standing is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 70% of all ranked servers, and #205 of the solo servers (top 91%). Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
·····W·
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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.
usual gap5.7 daysbetween real wipes
wipe-day peak2players, last three wipes
crowd held100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Sat 26 SepSun 20 Sep
Players each hour, from the hour of the wipe. The latest peaked at 2, 4 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 26 Sep, 06:49 UTC33d ago
2
–
running
0
Sun 20 Sep, 13:31 UTC38d ago
1
✓ held half
5.7 days
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Where in the world is Ural Battlefield (coming soon)?
Ural Battlefield (coming soon) leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 188.234.213.232:28015.
How reliable is Ural Battlefield (coming soon), and is it up?
You cannot join now: Ural Battlefield (coming soon) is offline, last seen 26 days 16 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 13 September 2026.
What Rust version is Ural Battlefield (coming soon) on?
The server Ural Battlefield (coming soon) is on Rust network protocol 2633 and build 163493 under Linux. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does Ural Battlefield (coming soon) reset?
Ural Battlefield (coming soon) has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 33 days 4 hours.
What happens on Ural Battlefield (coming soon) when wipe day arrives?
Recent wipes have peaked at 2 players on average. Peak numbers came 4 hours into the latest wipe. Above half the peak until the next wipe: that was the pattern in 100% of its recent wipes.
Player numbers
Where does Ural Battlefield (coming soon) place in the wider field of Rust servers?
Over the last seven days, Ural Battlefield (coming soon) has #15,929 for player hours, in the top 70% of all ranked servers. It comes #205 among servers in the solo group.
What does the population on Ural Battlefield (coming soon) look like?
It has been 26 days 16 hours since Ural Battlefield (coming soon) was last seen, and it is offline right now.
Tags and filters
What is meant by the tags on Ural Battlefield (coming soon)?
The game's browser takes its cue from the tags Ural Battlefield (coming soon) has set: gmrust (Game mode): Survival in the standard Rust style; mp500 (Max players): The server holds 500 slots; ts1 (Group limit): Teams cap out at 1; v2633 (Protocol): Join only if your game runs protocol 2633; cs163493 (Build): This runs on build 163493; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^i (Battlefield): PvP runs fast here, with kits and boosted rates; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does Ural Battlefield (coming soon) appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Ural Battlefield (coming soon) among them: Modded Rust servers, graded, Rust battlefield servers, graded and Solo Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Battlefield ^i, Modded ^z and Oxide ^o; Group limit: Solo.
Server rules
Which rules does Ural Battlefield (coming soon) enforce, and what are its settings?
The name of Ural Battlefield (coming soon) gives no gather rate. Solo play only, with no teams permitted. You get battlefield here, high rates and kits, for fast PvP. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map Ural Battlefield (coming soon) uses?
Ural Battlefield (coming soon) runs a map the game generates, procedural and size 4,500.
How to join
How do you get onto Ural Battlefield (coming soon)?
Enter client.connect 188.234.213.232:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp500,ptrak,$r?,v2633,^i,gmrust,cs163493,ts1,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp500
Max playersThe server holds 500 slots.
ts1
Group limitTeams cap out at 1.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs163493
BuildThis runs on build 163493.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Gameplay
^i
BattlefieldPvP runs fast here, with kits and boosted rates.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
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.
A fair term, with more to come. Strongest in wipe hold (A+); standing is the one to work on (F).