Honkai: Star Rail · Progression guide

Honkai: Star Rail Speed Breakpoints: 134 vs 160 SPD

A Speed target is useful when it changes an action you need before a particular deadline. Start with that deadline, then check the turn order, Skill Points and stats sacrificed to reach it. Here is how to compare two builds without treating 134 or 160 SPD as a rule for every character and mode.

Quick answer · Our advice

134 SPD gives a second natural turn at about 149.25 AV in the constant-Speed opening model. Four turns in a 250-AV window have an exact mathematical boundary at 160 SPD; the fourth turn then lands on the deadline. Check a margin, the actual combat SPD and any action manipulation before chasing a breakpoint. More turns help only if the team can use them.[1][2][4]

View active Honkai: Star Rail codes

By GachaLootGuide reviewed November 9, 2026

Version 4.6 context. Worked timelines use the ordinary Memory of Chaos 150/100 AV model, one uninterrupted window and constant SPD.

SPD sets the time to a turn; it is not a turn counter

In the baseline system, a full Action Gauge is 10,000 and Base Action Value is 10,000 divided by SPD. Lower AV means the next turn arrives sooner. After a normal action, the gauge resets; speed changes, advance and delay can alter the remaining wait.[1]

Our advice

Keep three numbers separate: the SPD used during the interval, the AV until an action and the AV budget before the relevant timer. A displayed “two-cycle” goal needs a definition of which cycles and wave you mean. It does not mean every character receives two turns.

The ordinary MoC model gives the opening cycle 150 AV and the next cycle 100 more. Our examples call these cycle 0 and cycle 1: together, their uninterrupted window is 250 AV. This window is not a universal clock for every game mode.[2][3]

Where does the 134 SPD target come from?

Worked example · GachaLoot calculation

Fit two natural turns before 150 AV

Assumptions

Start from a full gauge, with constant SPD and no advance, delay, extra turn or wave transition.
The goal is to act twice before the ordinary opening MoC cycle ends at 150 AV.
Use exact values, then round the displayed calculations only for readability.

Time of the second turn2 × 10,000 ÷ SPD = 20,000 ÷ SPD AV
Mathematical boundary20,000 ÷ 150 = 133⅓ SPD
At 134 SPD20,000 ÷ 134 ≈ 149.2537 AV
Time left before the deadline150 − (20,000 ÷ 134) ≈ 0.7463 AV

Result: 134 crosses the two-turn boundary in this model. It does not guarantee a kill, a buffed attack or two actions in every subsequent 100-AV cycle.

Limits of this example: The strict “before” comparison avoids making a claim about an action tied with a timer. Real action manipulation and wave rules require a separate timeline.

Mechanic references[1][2]

Why 160 SPD needs more careful wording

Our advice

Ask what the number is supposed to buy. For four natural turns within the first 250 AV, solve 4 × 10,000 ÷ SPD = 250. The exact boundary is 160. At exactly 160.000 SPD, the fourth modeled turn occurs at exactly 250 AV. That is a tie, not a safely earlier action.

Fribbels’ own optimizer documentation notes hidden Speed decimals in manually entered or OCR-derived stats. An integer on a stat screen does not establish an exact value for a tight calculation. KQM also distinguishes the displayed AV rounding from the underlying gauge calculation.[4][1]

Our advice

Confirm the actual battle order before replacing a useful Relic to meet a spreadsheet target. A small margin makes the arithmetic easier to interpret, but the correct margin depends on the real values and modifiers. We show 161 as a simple comparison, not a mandatory new universal target.

Our suggested checks

Swipe across the table to see all columns.

Why 160 SPD needs more careful wording comparison
Exact SPD in this model	Natural turn times (AV)	Before the deadline
134	74.63; 149.25; 223.88; 298.51	2 before 150; 3 before 250.
160.000	62.50; 125.00; 187.50; 250.00	2 before 150; 3 before 250, plus one exact-boundary action.
161	62.11; 124.22; 186.34; 248.45	2 before 150; 4 before 250.

References[1][2]

Compare two constant-Speed timelines

Starts at a full 10,000 Action Gauge. Counts natural turns strictly before one deadline. It does not simulate a team, a wave transition, buffs or extra actions.

Build A: exact constant SPD

Use a decimal value if known. The displayed integer may conceal decimals.

Build B: exact constant SPD

This compares natural turns, without action advance or delay.

Deadline (Action Value)

150 for the opening MoC window; 250 includes the next 100 AV.

Build A

3 natural turns before the deadline · 74.63 AV per turn

Turn times: 74.6269, 149.2537, 223.8806 AV.

Next turn: 298.5075 AV.

Build B

4 natural turns before the deadline · 62.11 AV per turn

Turn times: 62.1118, 124.2236, 186.3354, 248.4472 AV.

Next turn: 310.559 AV.

Each turn must also be useful and affordable in Skill Points. Timing alone does not predict damage or a clear. Calculations stay in this page.

An extra turn must repay the stats you gave up

Worked example · GachaLoot calculation

The faster build wins one window and loses another

Assumptions

Illustrative damage-only comparison: Build A has 134 SPD and deals 10,000 damage per natural turn.
Build B has 161 SPD and deals 8,500 per natural turn after sacrificing other stats.
Both can afford all planned actions. No overkill, follow-up damage, buffs, enemy behavior or wave changes are modeled.

Build A before 250 AV3 × 10,000 = 30,000 modeled damage
Build B before 250 AV4 × 8,500 = 34,000 modeled damage
Build A before 150 AV2 × 10,000 = 20,000 modeled damage
Build B before 150 AV2 × 8,500 = 17,000 modeled damage

Result: The preferred build changes with the deadline. A fourth action at roughly 248 AV cannot help a fight that is already decided before 150 AV.

Limits of this example: These invented damage values demonstrate opportunity cost, not a benchmark. Damage from outside natural turns and team interactions can reverse the result.

Mechanic references[1]

Check who acts first and who pays for the actions

Our advice

Write the first few actions for the whole team. If your plan requires a support to apply an effect before the damage dealer acts, raising the damage dealer’s SPD can change that order. Then read how that particular effect expires; not every buff follows the same turn counter.

Use a small Skill Point ledger. In an illustrative plan starting with three available points and four intended skills costing one each, the fourth skill is not affordable without another source: 3 − 1 − 1 − 1 = 0 before it. A fourth natural turn can still happen, but its action may need to change.

KQM’s team-building reference treats SP generation and consumption as part of the rotation and documents kit exceptions. A natural action, an extra action and a specific skill use should not be counted as interchangeable.[5]

Our advice

Compare the existing build with one candidate change. Record the action you want, whether its buff is active and whether it can be paid for. Only then decide whether additional SPD addresses the team’s problem.

Action advance is not a flat number of AV

Worked example · GachaLoot calculation

Two different ways to shorten the same remaining wait

Assumptions

One unit currently has 4,000 Action Gauge remaining and 100 SPD.
Compare either raising its constant SPD to 125 now, or applying a 25% advance now while keeping 100 SPD.
These are separate alternatives, with no other queue effects.

Original wait4,000 ÷ 100 = 40 AV
Raise SPD to 1254,000 ÷ 125 = 32 AV remaining
25% advance removes gauge10,000 × 0.25 = 2,500 Action Gauge
Wait after that advance at 100 SPD(4,000 − 2,500) ÷ 100 = 15 AV remaining

Result: A 25% advance is neither “25 SPD” nor “25 AV.” Its effect depends on the unit’s gauge and SPD at that moment.

Limits of this example: Gauge cannot be advanced below zero. A full advance also interacts with queued actions. This example does not resolve those queues or repeated advances.

Mechanic references[1]

When to stop using the simple MoC timeline

HoYoverse’s 4.6 notice describes an Apocalyptic Shadow phase in which breaking a protected target advances allies’ actions. That is an explicit stage-rule reason a constant-Speed schedule will not describe the whole battle.[6]

Our advice

Rebuild the sequence when the relevant mode changes the clock, a new wave changes the timing situation, an enemy delays a unit or a skill advances an ally. The calculator deliberately models one uninterrupted window; it does not add separate waves together.

Use combat SPD for the interval you are analyzing. A temporary buff that expires between turns cannot be treated as permanent. For tight timings, enable the AV display and inspect the actual action order rather than relying solely on an out-of-combat number.[1]

HSR Speed breakpoint questions

Does every character need 134 SPD?

Our advice: No. It solves a particular opening-window problem under stated assumptions. Judge the character’s role, action sources, team order and stats sacrificed against the deadline you actually need.[1]

Is exactly 160 SPD safely four turns before 250 AV?

Our advice: The unmodified formula places turn four exactly at 250. Our conservative model lists that boundary action separately. Check real precision and combat timing instead of treating equality as safely earlier.[1][4]

Is Speed between breakpoints wasted?

Our advice: It still changes action timing, and that can matter for teammate or enemy order. A chosen cycle-count table captures only one kind of deadline, not every useful timing interaction.[1]

Can I use this calculator for action-advance teams?

Our advice: Use it only for the constant-Speed baseline. The moment an advance, delay, changing buff or wave rule affects the unit, calculate that event separately or inspect a more complete battle timeline.[1][6]

Sources and review scope

KQM supplies the action-gauge mechanics; its launch-era character recommendations and universal 120-SPD advice are not adopted. The MoC window is cross-checked against Luxmiyu’s timing reference and an explicitly versioned community explanation. HoYoverse’s 4.6 notice supplies a current example of mode-specific action advance. We calculate our own timelines, keep exact-boundary actions separate and do not claim that the tool simulates tie ordering, every wave transition or a live team clear.

Review dates describe this article and its references, not hands-on testing of a game account. Passages marked “Our advice” are GachaLoot’s recommendations. Check the current kit, challenge rules and upgrade preview for your own account.

[1] How Do Speed and Turn Order Work in Honkai: Star Rail?
KQM — independent mechanics research · Checked November 9, 2026
The 10,000 Action Gauge model, SPD/AV relationship, advance, delay and changing SPD. Launch-era build rankings, 120-SPD prescriptions and old set priorities are excluded.
[2] Speedtune — timing and cycle model
Luxmiyu — independent timing reference · Checked November 9, 2026
The ordinary 150-AV opening and subsequent 100-AV window. Its old character presets are not adopted. We derive our own strict-before comparisons.
[3] Putting the Express in Astral Express — Star Rail 1.1
HoYoLAB — community-authored mechanics explanation · Checked November 9, 2026
Historical cross-check of the MoC cycle-window definition. Hosting on HoYoLAB does not make this an official publisher guide.
[4] Optimizer guide — manually entered and OCR Speed precision
Fribbels — optimizer project documentation · Checked November 9, 2026
The project warns that in-game Speed decimals can be hidden in manually entered or OCR inputs. No software installation or account import is required by our tool.
[5] Honkai: Star Rail Teambuilding Guide
KQM — independent reference · Checked November 9, 2026
Rotation-level SP supply and demand and the existence of kit exceptions. Old named-team meta and exhaustive skill rules are excluded.
[6] Version 4.6 Update Details — mode rules
HoYoverse — official update notice · Checked November 9, 2026
Version context and the announced Apocalyptic Shadow weakness-break action advance. That phase-specific rule is not applied universally or advertised as a permanent reward offer.

Keep reading

All game guides

Currencies & resources

Honkai: Star Rail Stellar Jade, Passes & Fuel Guide

Compare Star Rail Passes and Special Passes, Stellar Jade, Credits, EXP items and Fuel. Understand which part of an HSR reward funds Warps or upgrades.

Redemption & troubleshooting

How to Redeem Honkai: Star Rail Codes on Android & iOS

Find the HSR redemption menu on Android, use the official gift website on iOS, and check mail or Currency Record when a code reward seems missing.

Gameplay & upgrade decisions

Honkai: Star Rail — Traces or Relics First? What to Upgrade

Choose between Traces, Relics, character levels and Light Cones in Honkai: Star Rail, with upgrade priorities, worked examples and a farming checklist.

Gameplay & upgrade decisions

Honkai Star Rail Energy Regeneration Rope or ATK Rope?

Compare an ERR Rope and an ATK Rope across a full Ultimate rotation. Separate repeatable Energy, fixed grants and conditional hits before you swap.

Gameplay & upgrade decisions

Honkai: Star Rail Relics — Should You Craft, Reroll or Keep Farming?

Decide when to use Self-Modeling Resin, Variable Dice or Trailblaze Power. Compare an ERR Rope, a +15 reroll and a two-character farming budget.

View current Honkai: Star Rail codes