On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average0peak 3
Rank#4,130top 19% · #695 in NA
Last wipe12d agobiweekly schedule
Next wipe1d 1hThu 29 Oct, 20:51 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 100 on average. Plenty of space to grow.
Standingrank on player hours
81/ 100
B+
Holds a respectable place: #4,130 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
14/ 100
F
Needs to work on its frame rate: 8 server fps on average.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
45/ 100
D
Slipped a little: down 378 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in uptime (A+); population 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.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
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 20 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 19% of all ranked servers, top 37% in NA. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···F···
·······
···W···
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Thursday 29 October, 20:51 UTC, in 1d 1h.
Its biweekly schedule tag · low confidence
usual gap14.1 daysbetween real wipes
wipe-day peak4players, last three wipes
crowd held0%else halves by day 5
Coming wipes
1d 1hThu 29 Oct, 20:51 UTC
7d 23hThu 5 Nov, 19:00 UTCFW
15d 1hThu 12 Nov, 20:51 UTC
29d 1hThu 26 Nov, 20:51 UTC
35d 23hThu 3 Dec, 19:00 UTCFW
43d 1hThu 10 Dec, 20:51 UTC
The first 48 hours of its last wipes
Thu 15 OctThu 1 Oct
Players each hour, from the hour of the wipe. The latest peaked at 3, 3 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 15 Oct, 20:51 UTC12d ago
3
–
running
0
Thu 1 Oct, 17:57 UTCFW27d ago
5
halved by day 5
14.1 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
In what location does Dallas Rust Large | Biweekly sit?
The NA tag on Dallas Rust Large | Biweekly puts it in North America. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 66.51.99.75:28035.
How dependable is Dallas Rust Large | Biweekly, and is it online at the moment?
The server is up: Dallas Rust Large | Biweekly is online now. According to its reported uptime, the last restart was about 5 hours ago. It was up 168 of 168 hours over the last 7 full days, which is 100% of the time. It was first seen by Rust Server Score on 20 September 2026.
Is Dallas Rust Large | Biweekly smooth to play on?
It averaged 8 server fps over the last 48 hours, with a low of 5. Up to 116,814 entities were in the world, covering buildings, deployables and the rest. At its highest, it used 3,546 MB of memory. Lag is what players feel when fps is low and the entity count climbs.
On what Rust version does Dallas Rust Large | Biweekly sit?
You will find Dallas Rust Large | Biweekly on Rust network protocol 2635 and build 168909, hosted on Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
How frequently does Dallas Rust Large | Biweekly wipe its map?
The prediction follows its tag, because too few of Dallas Rust Large | Biweekly's wipes are on record to confirm the schedule. It is due to wipe next on Thursday 29 October at 20:51 UTC. 12 days 22 hours have passed since this world was made. Its tags give a wipe schedule of every two weeks.
What should you expect from wipe day on Dallas Rust Large | Biweekly?
Recent wipes have peaked at 4 players on average. The crowd on the latest wipe was largest 3 hours after it began. Above half the peak until the next wipe: that was the pattern in 0% of its recent wipes. The crowd dropped below half by day 5 in the wipes where it did not hold.
Player count
What position does Dallas Rust Large | Biweekly hold in the rankings?
Over the last seven days, Dallas Rust Large | Biweekly has #4,130 for player hours, in the top 19% of all ranked servers and #695 in North America.
How many players does Dallas Rust Large | Biweekly usually have?
With 100 slots available, Dallas Rust Large | Biweekly currently has 0 players. Averaging 0 players over seven days, it peaked at 3. The busiest time in the last 48 hours was 02:00 UTC, with an average of 1 players.
Tags
What do Dallas Rust Large | Biweekly's tags stand for?
The game's browser takes its cue from the tags Dallas Rust Large | Biweekly has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): 100 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^b (Biweekly): A wipe happens once a fortnight; ^v (Vanilla): You get the unmodified game: no rate changes, no kits, no rule changes; ^q (Premium): You need Rust's premium status to get in; ^o (Oxide): Plugin framework: Oxide (uMod); NA (North America): You will find it under North America in the browser; sc1 (Custom tag): Not one of Rust's standard tags, it comes from a plugin or the owner. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does Dallas Rust Large | Biweekly appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Dallas Rust Large | Biweekly among them: Best community servers, graded, North America Rust servers, graded and Vanilla Rust servers, graded. These filters bring it up on the server list: Region: North America; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Game mode: Premium; Server tag: Biweekly ^b, Vanilla ^v, Premium ^q and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.
Rules and settings
Which rules does Dallas Rust Large | Biweekly enforce, and what are its settings?
You will find no gather rate in the name of Dallas Rust Large | Biweekly. With no change from the game default, groups take up to 8 players. It runs survival, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it under Community, as a community server. Plugins on it number Oxide. The vanilla label is its own: you get the unmodified game: no rate changes, no kits, no rule changes. You need Rust's premium status to get in. VAC, Valve's anti-cheat, is enabled.
Which map is in play on Dallas Rust Large | Biweekly?
A procedural map of size 4,200 and seed 1337, generated by the game, is what Dallas Rust Large | Biweekly runs. A matching size and seed produce the same map, viewable on RustMaps from this page. The name of the map reads: Dallas Rust Large.
Connecting
How should you connect to Dallas Rust Large | Biweekly?
To connect, start Rust, press F1, and type client.connect 66.51.99.75:28035. Or click Launch Rust here, which launches Rust through Steam and joins you. You need Rust's premium status to get in. You can find its website at https://discord.com/invite/4Hp3e9Hk7v.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,^b,^v,NA,gmrust,cs168909,^q,sc1,ts8,^o
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp100
Max players100 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Wipe schedule
^b
BiweeklyA wipe happens once a fortnight.
Difficulty
^v
VanillaYou get the unmodified game: no rate changes, no kits, no rule changes.
Mods and access
^q
PremiumYou need Rust's premium status to get in.
^o
OxidePlugin framework: Oxide (uMod).
Region
NA
North AmericaYou will find it under North America in the browser.
Other
sc1
Custom tagNot one of Rust's standard tags, it comes from a plugin or the owner.
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 term to build on. Strongest in uptime (A+); population is the one to work on (F).