GUIDES · BETSLIP DOCTOR
Which price describes my saved ticket when the current market has moved?
If the saved ticket shows its own captured quote, that price describes the saved version. A current market quote describes the market now; it does not by itself tell you what price was attached to the saved ticket. Compare the same selection and note when each value was observed. BSD's cited live-state source uses a current in-play quote only as one input to event-status classification; it does not define saved-ticket price storage or promise a separate price-history display.
For Bettors comparing a saved ticket with a market that has moved · Updated
Use the saved ticket's own quote for its saved version
A saved ticket and a live market answer different questions. The price shown on the saved ticket, when that record supplies one, describes the ticket version you are reviewing. Keep that value tied to the saved selection and the time recorded with it.
Do not replace the saved ticket's historical quote with a number from a later market check. A newer quote can move while the saved selection remains the same.
Treat the current quote as a separate market snapshot
A live price is about the market at the time it was observed. It may differ from a saved ticket's quote, and seeing it does not establish that the saved record was repriced or that the new number applies to that ticket.
Compare the same event and selection, then keep the saved value and current value labeled by their own timestamps. The source does not guarantee that a live quote will be available or unchanged when you review it.
A live-state signal is not a saved-ticket price
The recorded live-state code can use the presence of a current in-play quote to help infer whether an event has started when scoreboard status is unavailable. That signal is part of event-state logic; it is not a record of the price on a saved ticket.
If the ticket view does not expose its own captured price, the live-state source cannot reconstruct it. Do not guess the historical value from the current board.
Hypothetical: a market moves after a ticket is saved
Imagine a bettor saves a ticket and checks the same selection later, after the market has moved. The saved ticket's captured quote describes the saved version if it is shown; the later quote describes the market at the later observation time. The bettor keeps those values separate and does not treat the current quote as the historical ticket price.
Related questions
Does a current live quote tell me what price was saved?
No. A current quote describes the market when observed. Use the saved ticket's own recorded value for its version if that value is available.
Does BSD's live-state data update a ticket price?
The cited live-state source derives event status and can use an in-play quote as a status signal. It does not specify saved-ticket price storage or price-history display behavior.