Games: 973 titles in the captured catalogue

The captured catalogue is a CSV of one row per rendered game card on the public lobby. Each row carries the provider_name the operator assigns, the game_id the operator generates, the capture_date the script logged, and the snapshot fields rendered into the card at that moment. The 973 figure is a count of unique game_ids after deduplication against the raw rendered list. The 8 figure is a count of distinct provider_name values inside the same CSV.

Comparative analysts who work with this kind of capture should expect the CSV to drift across runs. Provider rosters change; cards are added, retired or relabelled; the operator product may render the same game_id under a slightly different display label between releases. myteam11app.com treats the 17 August 2026 capture as the citation for the editorial product; the next capture overwrites it. Anyone comparing this route to the in-app product should cite the date both sources were last opened.

Three caveats apply before reading further. First, the capture is one render, not a panel: only fields the operator surface exposed at that moment are present. Second, the count is unique game_ids, not unique display labels: a renamed title still counts as one. Third, the provider_name values are taken as written, with the operator casing preserved; the 8-provider count is therefore literal, not normalised.

Eight providers sit behind the 973-row lobby. The table below lists each provider alongside the count of unique game_ids captured in the CSV. The matrix is sorted by descending count; the totals row is the deduplicated total across all eight providers.

The lobby uses server-side URL parameters, not client-side toggles. Each chip at the top of the route is a clean link to a filtered URL, and the link is the contract: the route the link opens carries only the named filter. There is no JavaScript-only state to keep in sync; the URL is the truth.

The available filters match the eight providers in the matrix above:

• ?provider=Evolution narrows the lobby to Evolution's 373 captured titles.
• ?provider=JILI narrows the lobby to JILI's 231 captured titles.
• ?provider=PG%20SOFT narrows the lobby to PG SOFT's 152 captured titles.
• ?provider=Fachai narrows the lobby to Fachai's 75 captured titles.
• ?provider=Pragmatic%20Play narrows the lobby to Pragmatic Play's 70 captured titles.
• ?provider=YellowBat narrows the lobby to YellowBat's 58 captured titles.
• ?provider=KOOLBET narrows the lobby to KOOLBET's 11 captured titles.
• ?provider=Originals narrows the lobby to Originals's 3 captured titles.
• No parameter (or ?provider=all) returns the full 973-row lobby.

The filter parameter is case-sensitive in the editorial product because the operator rendering was case-sensitive in the captured CSV. evolution (lowercase) returns the full lobby because no provider matches that name; Evolution (capitalised) returns the 373-row subset. The casing on every chip above matches the casing the operator product used.

Within a filtered provider subset, the rendered rows are ordered alphabetically by the captured display label. Alphabetical order in this context means a byte-sort of the label as rendered; the operator surface does not expose a separate sort key, and the capture does not derive one. Reverse alphabetical order is exposed by appending &sort=desc, which mirrors the descending sort the operator renders for some provider pages.

Sharding is the practical effect of that ordering: large providers such as Evolution and JILI produce long pages, and the rendered grid is split into multiple visual sections inside the provider surface. The capture keeps the rendered shard boundaries so that the editorial product reproduces the same page structure when the URL parameter is set.

If the operator product changes its ordering rule between captures, the next capture will reflect the new order, and the editorial product will update on the next refresh cycle. Treat the rendered sort as the operator's choice, not as a property of the editorial product.

Each captured row in the catalogue has a per-game profile on a route under /games/{slug-id}/. The profile is built from four fields that always appear in the captured CSV, plus a small set of conditional fields that appear only when the operator surface rendered them.

The four always-present fields are:

• provider_name: the operator's label for the studio, taken as written. Eight values appear in the lobby; this field drives the provider matrix above and the ?provider= filter.
• game_id: the unique identifier the operator assigns to the rendered card. Used as the trailing segment of the slug and as the dedupe key in the count of 973.
• capture_date: the date the row was pulled. Every route under /games/{slug-id}/ carries the same capture date stamp on the route footer.
• format family: the format the operator renders into the card thumbnail. Values seen in the captured lobby include slot, live, table, crash, fishing and instant.

The conditional fields are the ones that only render on a subset of cards: live-dealer flags, jackpot tags, free-play availability and the in-app bonus opt-in. None of those conditional fields change the 973 count; they are descriptive labels rendered next to the same game_id. myteam11app.com carries the conditional fields on the per-game profile when the operator surface rendered them.

Three reading angles work well with a captured catalogue of this shape. They are not the only angles, but they are the ones that survive the most comparison without becoming marketing copy.

Lobby density is the count of unique game_ids per provider relative to the total of 973. Evolution at 373 is dense; Originals at 3 is sparse. Density is a measure of how much of the lobby a single provider occupies, not a measure of which provider is best. Density tells you what the operator has signed with that studio.

Provider curve is the shape of the count distribution across the eight providers. A curve dominated by two providers (Evolution and JILI at 373 and 231) means the operator has built the bulk of the lobby around two studios, with the remaining six as long-tail variety. A flatter curve would mean broader distribution; the captured curve is steep.

Snapshot freshness is the gap between the capture date on this route and the date a reader opened the in-app product. The wider the gap, the more likely the in-app catalogue has drifted from the 973 figure. Always cite both dates when comparing.

The captured catalogue and the in-app catalogue are not the same set. The capture is a single render of the public lobby on 17 August 2026; the in-app product continues to receive new titles, retire old titles and rebalance provider rosters between captures. The snapshot is the reference; the live set is what the operator renders to a logged-in player today.

For most of the year, the captured reference and the live set are close enough to use the captured reference for editorial reading. Around major provider release windows, the gap can be larger, and the per-game profile may carry a notice that the displayed fields reflect the captured render rather than the in-app value.

The capture is not a marketing artefact; it is a citation. myteam11app.com treats it that way throughout the editorial product: every route that quotes a dynamic value carries the capture date in the footer, and the next capture will overwrite the existing one in the standard refresh cycle.

The captured lobby exposes a small set of risk-shaped choices that any reader should weigh before playing. They are not promotional numbers; they are the standing-reading cues the operator surface renders into the cards. Three are worth naming here.

Hold-coins modes: a subset of slots on the captured lobby expose a hold-coins mode that pauses the spin cycle at a partial payout and lets the player choose to collect or continue. The operator surface labels the mode on the card; the per-game profile reproduces the label and the rules. Whether to use hold-coins is a player choice; the editorial product does not recommend either branch.

Free-play availability: a subset of slots on the captured lobby expose a free-play entry point inside the in-app lobby, where the operator surfaces a demo session that does not deduct the wallet. Free-play is a useful way to read the format before staking real money; it does not simulate the full payout distribution because the in-app RNG seed is shared with real-money play in most releases.

Live-dealer pacing: live-dealer titles on the captured lobby expose the round cadence the studio uses. Pacing is a reading angle only; it does not change the underlying probability. myteam11app.com does not invent bonus values on top of the captured pacing; the per-game profile quotes the rendered value.

The lobby is one route in a wider editorial product. Six routes are worth opening alongside it because they quote fields the lobby alone cannot.