Back-to-Back Fatigue Calculator

Start with the market definition

Use this page when the task is to apply explicit rest, travel, and lineup adjustments to a baseline projection. At this stage, a market comparison still requires an available price for the identical selection and period.

Back-to-Back Fatigue depends on the event scope represented by Baseline team or player projection and Standard deviation.

For the saved case, the calculation uses adjusted projection = baseline × combined rest, travel, and rotation factors.

This specialized model addresses the narrow question named by the calculator.

It is an arithmetic reference rather than a full simulation.

For this market, use a separate scenario for a plausible upper or lower assumption.

The Basketball Moneyline Model is useful only if that separate output affects the decision.

What can move the baseline

Under the entered assumptions, a material participant, format, or source change requires a new fatigue-adjusted projection baseline.

On this page, expected minutes, starting status, usage, pace, and opponent information need to refer to the same game.

Within this calculation, a lineup change can affect playing time and team efficiency, so avoid applying the same news twice.

Entries required for the result

Keep Baseline team or player projection on the event basis defined here: projection before rest adjustment. Label Back-to-back penalty as observed, quoted, or projected. Its role is expected percentage reduction. Travel penalty belongs to the same period as the other entries. It is additional percentage reduction.

Rotation offset records positive adjustment for lineup or rest advantages. Market line is a separate input defined as line compared with adjusted projection. Standard deviation is a separate input defined as expected variation.

In the current scenario, inputs collected on different dates may describe states that never existed together.

Example calculation

When using the result, this worked case verifies the method without describing a typical market.

For the Back-to-Back Fatigue Calculator, this independent example exists to verify the arithmetic. On this page, its inputs are illustrative rather than a forecast for a current event.

Baseline team or player projection is set to 127.68 points for this worked case.

Back-to-back penalty is set to 2.7% for this worked case.

Travel penalty is set to 0.94% for this worked case.

Rotation offset is set to 0% for this worked case.

Market line is set to 98.735 points for this worked case.

Standard deviation is set to 10.5 points for this worked case.

Applying the Back-to-Back Fatigue rule: adjusted projection = baseline × combined rest, travel, and rotation factors. The example values produce 123.06.

Probability over reference line is 98.98%. Net adjustment is -3.61%. Fair over odds is -9658.

For this fatigue-adjusted projection example, keep the unrounded example inputs until the calculation matches, then apply the same unit checks to current data.

Within this calculation, reproduction confirms arithmetic, not event assumptions.

A cautious second case

Under the entered assumptions, choose the least certain field and run one adverse case with other entries fixed.

For this market, keep the new answer beside the baseline.

For the saved case, a format, roster, participant, or settlement change calls for a new baseline.

Using the result cautiously

The headline answers the arithmetic question and supporting rows add context.

Neither confirms market availability.

At this stage, compare only after confirming same event, selection, and settlement period.

When using the result, save enough context to reproduce fatigue-adjusted projection without form defaults.

In the current scenario, start a new case when period, participant, settlement rule, or source definition changes.

Within this calculation, a timestamped baseline remains useful when no wager follows.

Reasons to calculate again

Fatigue effects vary by team, player, travel distance, and rotation.

On this page, verify whether the wager covers a game, half, quarter, or player performance and whether overtime counts.

When using the result, the calculation cannot verify whether every source was collected at a compatible time.

Questions about the inputs