BetSlip Doctor

GUIDES · BETSLIP DOCTOR

Why can a ticket count differ from the number of selections in History?

Because a ticket and its legs are different things. BSD stores one multileg parlay as one History record and keeps its individual selections inside that record. One saved parlay can therefore count as one ticket and several legs. A Grade is a second opinion, not a pick.

For Bettors comparing a saved ticket count with its selection or leg count · Updated

Count the ticket once, then count what is inside it

A History record represents the saved sportsbook ticket. Its legs represent the selections that make up the ticket. The imported record is built from the sportsbook ticket's selections; an entered record is built from the saved ticket's selections. Those are two levels of the same record, rather than two separate sets of bets.

For example, a parlay ticket with three selections is one ticket record containing three legs. If the question is how many tickets you saved, count the records. If it is how many selections they contain, count the legs within them.

Open the row to check the leg count

In History, look at the ticket row. A multileg row can show a count chip. Open the record to see its Legs section and the selections held inside. If a ticket has more than one leg, its row can still be a single ticket in the list.

Saved research reports are separate from recorded bets. If a History view shows both types, do not add a report to the number of ticket records.

  • One row or record answers how many saved tickets are represented.
  • The Leg count chip or Legs section answers how many selections are listed inside that ticket.
  • If a source has not supplied selections yet, BSD can show an incomplete imported record with no legs available to inspect.

Compare the same ticket before assuming a selection is missing

Open the specific History record and compare its sportsbook, ticket type and selection list with the original sportsbook entry. A difference between one ticket and multiple legs is expected for a parlay. A leg that is absent from the opened record is a different question from how many ticket rows appear in History.

A count does not settle a bet or verify a result

This count only explains the record structure. It does not establish that every selection or settlement detail was supplied by the sportsbook. The record may show an incomplete state or a source limitation. Check the details shown on that particular row before drawing a conclusion about its result.

Illustrative example: one ticket, three legs

Imagine a saved parlay containing three selections. History can show one ticket row with a three-leg indicator. The correct counts are one ticket record and three listed legs. If you need to check which selections are present, open that row and read its Legs section. This is a synthetic example, not a customer record or a betting outcome.

Related questions

Does each leg get its own History row?

A multileg ticket is stored as one record with its legs inside it. Open the record to inspect the selections rather than treating every leg as a separate ticket.

Why does an imported ticket show no legs?

An imported record can be incomplete when its source has not supplied the selections. Check the record's status and limitations; the missing list does not prove that the sportsbook ticket had no selections.

Sources and further reading

Explore BSD research.

Review supported ways to use BSD.