Blog · Bac Bo Live

Bac Bo history: how to query and store every round

Where to see the Bac Bo Live results history, why pages keep so little, and how to pull and store every round through the API, in Python.

Published on October 18, 2026 · 4 min read

The Bac Bo history is the list of rounds that have already happened at the table, with each side's dice, who won and what the tie paid. On the table itself and on most sites you only see the last few dozen rounds — enough for a glance, but too little for any serious statistics or to feed a bot. In this article you will see where each kind of history lives and how to build your own, complete, from the API.

Where to see live Bac Bo results

  • On the table itself: the game shows recent rounds as charts, the so-called roadmaps, which we explain in Bac Bo charts.
  • On statistics sites: they show the last few hours with filters, but each one keeps a short period and not all of them record every round. In our round-by-round comparison, the public list of a well-known site was leaving out about 20% of the rounds.
  • On LynxMetrics' Bac Bo Live page: the latest rounds and the statistics refresh by themselves, free, for anyone.
  • On the API: every round since 14 October 2026, in JSON, for your program to query.

Why a long history makes a difference

With 100 rounds, a tie percentage of 15% can be pure chance. With 10,000, it lands close to the table's real value, which the game's maths puts at 11.27%. Across the 9,672 rounds we stored between 14 and 18 October 2026, the tie came up in 11.19% of them, almost exactly as expected — and that only shows up with a large sample. The same goes for how often each multiplier appears, for streak lengths, and for testing any idea before putting it in a bot.

How much history the Bac Bo Live API keeps

PlanHow far backRounds per request
2-hour trial7 days, like Proup to 250
Pro, R$ 21.90 per month7 daysup to 250
Business, R$ 49.90 per monthEverything, since 14/10/2026up to 1,000

A Bac Bo table runs about 2,500 rounds a day, so 7 days is close to 17,500 rounds, and the full history on Business grows by that much every week.

How to pull the history in pages

The /results endpoint returns rounds newest first, and includes a nextCursor. To fetch the next page, you pass that cursor in before, until it comes back null.

download_history.py

import json
import os
import time
import requests

API = "https://api.lynxmetrics.com/v1/bacbo-live"
HEADERS = {"x-api-key": os.environ["LYNX_KEY"]}

rounds = []
cursor = None
while True:
    params = {"limit": 250}
    if cursor:
        params["before"] = cursor
    r = requests.get(API + "/results", headers=HEADERS, params=params, timeout=30)
    if r.status_code == 429:
        time.sleep(int(r.headers.get("Retry-After", "5")))
        continue
    r.raise_for_status()
    page = r.json()
    rounds.extend(page["data"])
    cursor = page["nextCursor"]
    if cursor is None:
        break

with open("bacbo_history.json", "w") as file:
    json.dump(rounds, file)
print(len(rounds), "rounds saved")

How to keep the history up to date without repeating rounds

Once you have downloaded everything, you do not need to download it again. The after parameter takes the id or the settledAt of the last round you already have and returns only the ones that ended after it, oldest first. Run it periodically and your database stays identical to ours, with nothing skipped or repeated.

def new_rounds(last_id):
    r = requests.get(API + "/results", headers=HEADERS, params={"after": last_id, "limit": 250}, timeout=30)
    r.raise_for_status()
    return r.json()["data"]

If the page comes back full, call it again with the nextCursor in after, until it comes back null. For live following, the stream already covers short outages on its own, as explained in Bac Bo results in real time.

Where to store it

  • A JSON or CSV file: enough for analysis in Excel, Google Sheets or a notebook.
  • SQLite: a single file, no server, and it already supports queries like "how many 88x ties came up per day".
  • Postgres or another database: for sites and bots with many users. Use the round's id as the primary key, and a repeated round never gets in twice.

If your goal is to show the history on a site or in a spreadsheet, the walkthrough is in how to build a Bac Bo statistics site, dashboard or spreadsheet.

Frequently asked questions

How many rounds does the Bac Bo history show?

It depends where you look. The table and the statistics sites show the last few dozen rounds or a few hours, while the LynxMetrics API keeps every round since 14/10/2026, with 7 days of access on Pro and the full history on Business.

Can I download the Bac Bo history into Excel?

Yes. You download the rounds as JSON through the API and convert them to CSV, which Excel and Google Sheets open directly, or you pull the data straight into Google Sheets, as shown in the article about spreadsheets and dashboards.

Does the Bac Bo history help predict the next result?

No. Every round is independent, so the history is for statistics and verification, not for predicting the next round.

For adults 18 and over only. LynxMetrics is not affiliated with Evolution or with the casinos that offer Bac Bo Live, and it only sells data and stats, never predictions or betting tips, because every round is random and past results do not predict the next one.

Read also