ThamesQuill
18+

Five axes · Live-account testing · No vendor data · Refreshed each tournament cycle

How the ThamesQuill scoring grid is compiled — the five-axis assessment protocol

Every element of every operator score is derived from funded-account live testing conducted during an active tournament window. This page discloses the complete methodology: what is measured, how it is measured, and how axis weights were determined.

Protocol overview

ThamesQuill operates funded accounts at each operator in the benchmark cohort. All accounts are subject to the same standard onboarding conditions as any retail customer — no preferential treatment is requested or accepted. Testing is conducted during an active tournament window (typically Wimbledon fortnight and one ATP 500 event per cycle) to ensure that market depth, latency, and system stability are assessed under live tournament load, not during quiet periods when operator infrastructure is underutilised.

Scoring is conducted by two members of the editorial team independently; discrepancies of more than 0.3 on the 0–10 point scale for any sub-criterion trigger a third-party review session. The final score for each axis is the arithmetic mean of the two independent assessments when they agree within tolerance. The five axes and their assigned weights are fixed for the current methodology version (v2.0, published October 2022, last revised March 2024) and cannot be altered mid-cycle in response to operator performance or commercial developments.

01

Tennis market depth

Weight: 30% of composite score

Market depth is the primary differentiating factor for tennis-specialist bettors and carries the largest weight in the ThamesQuill model. An operator that offers only match-winner and a handful of pre-match set-betting lines cannot compete on the axis that matters most to the audience this site serves.

What is counted: During each audited match (minimum three matches per operator per cycle, all during live tournament play at a named Grand Slam or ATP 500 event), a count is taken of all currently available in-play markets — including match-winner, set betting, game handicap, break-of-serve, next-game winner, total games in set, and any specials offered by the operator. The count is recorded at a standardised point: 15 minutes after the first set begins, to allow the market to fully populate from the pre-match state. The count is repeated at two further standardised points: at the start of the second set and at any point where the match reaches a decisive set.

Scoring rubric: 40+ concurrent markets = 9–10 points. 30–39 = 7–8 points. 20–29 = 5–6 points. 15–19 = 3–4 points. Below 15 = 0–2 points. The score is weighted for the quality of markets (whether deep or specialist markets such as game handicap and break-of-serve are available, not just match-winner and set betting) as well as raw count. An operator with 25 markets that includes break-of-serve and game handicap in play scores higher than one with 28 markets that excludes these categories.

02

Withdrawal throughput

Weight: 25% of composite score

Withdrawal speed is the second-highest weighted axis because it represents the most practically consequential variable for a bettor who has had a successful session: the speed at which winnings become available for personal use. Operator-published withdrawal windows ("up to 3 working days") are aspirational; the ThamesQuill protocol measures actual settlement timestamps.

Test protocol: Ten withdrawal transactions per operator per cycle, across a minimum of two different payment rails (Visa Debit, PayPal, bank transfer where available). Transactions are initiated at the same time of day (Tuesday–Thursday, 10:00–14:00 GMT/BST) to minimise day-of-week banking variation. The timestamp is recorded from the moment the withdrawal is confirmed in the operator interface (status: "processing") to the moment funds appear as available in the receiving account. The median and 90th-percentile timestamps are recorded; scoring uses the median as the primary metric and the 90th-percentile as a reliability indicator.

Scoring rubric: Median under 2 hours = 9–10 points. 2–6 hours = 7–8 points. 6–24 hours = 5–6 points. 1–3 working days = 2–4 points. Above 3 working days = 0–1 points. A bonus 0.5 points applies where the operator offers a same-day guaranteed withdrawal rail (e.g. a proprietary instant-withdrawal product). A penalty of 1 point applies if any of the ten test transactions exceeded seven calendar days without operator explanation.

03

Cash-out latency

Weight: 20% of composite score

Cash-out latency — the elapsed time between confirming a cash-out request and the operator confirming settlement — is a material variable for in-play tennis bettors because market odds can shift significantly within the confirmation window. A latency of 0.9 seconds versus 3.4 seconds represents a 2.5-second window during which the live market price can move; on a fast-moving set, the difference in available cash-out value across that window can be non-trivial.

Test protocol: Ten cash-out transactions per operator per cycle, all conducted during live in-play sessions at a named tournament. Transactions are timed from the moment the "confirm cash-out" button is tapped (recorded via screen capture timestamp) to the moment the "cash-out confirmed" or equivalent success state is displayed in the operator interface. Pending states are not counted as confirmed; the timer runs until the definitive confirmation state is reached. Median and 95th-percentile are recorded.

Scoring rubric: Median under 1.0 second = 9–10 points. 1.0–2.0 seconds = 7–8 points. 2.0–2.5 seconds = 5–6 points. 2.5–3.5 seconds = 3–4 points. Above 3.5 seconds = 0–2 points. Partial cash-out availability adds 0.5 points; confirmed technical failures during the test session subtract 1 point per incident (maximum −2).

04

UKGC compliance posture

Weight: 15% of composite score

UKGC compliance posture assesses how effectively each operator implements its legal obligations under the UKGC's Social Responsibility Code (SRC) §3.4–3.9 and the Licence Conditions and Codes of Practice (LCCP). This axis does not reward operators for marketing compliance statements; it is scored on observable in-account behaviour during funded-account testing.

What is assessed: (a) Prominence of deposit-limit controls in the account navigation — scored from 10 (prominent, one-tap access from dashboard) to 0 (buried under three or more menu levels); (b) Self-exclusion flow — measured from the point of initiating a self-exclusion request to confirmation of the exclusion being activated; operators that route through a customer support call score lower than those with a fully self-serve flow; (c) Reality-check notification — whether time-in-session notifications appear as mandated by UKGC SRC 3.4.4 and whether they are interruptive (i.e., require acknowledgement rather than passive display); (d) Responsible gambling message prominence on in-play betting screens — whether "when the fun stops, stop" or equivalent messaging is visible without scrolling during an active in-play session; (e) Age-verification gate — assessed at registration for friction, accuracy, and whether the gate can be bypassed by any means observable during the audit session.

Scoring: Each of the five sub-criteria is scored 0–10 and weighted equally within the axis. The axis score is the mean of the five sub-criterion scores, normalised to the axis weight in the composite.

05

Mobile interface quality

Weight: 10% of composite score

Mobile interface quality assesses the usability and technical performance of each operator's mobile product during in-play tennis betting on a standard mid-range smartphone (current test device: a standard Android handset running current Android OS release, 4G connectivity, no Wi-Fi). This axis carries the lowest weight because the variance between operators' mobile products has narrowed significantly since 2019; most UKGC-licensed platforms now meet a threshold of adequacy that does not produce the differentiating factor it once did. It is retained because outlier failures — mis-tap-inducing button layouts, render lag during rapid in-play price updates, or crash events during peak tournament load — remain material consumer experience failures.

What is assessed: (a) Touch-target compliance — are all interactive elements (bet placement buttons, cash-out confirm, market toggle) at least 44×44 CSS pixels? Measured via browser developer tools; (b) In-play price render speed — the elapsed time between a market price change (confirmed via the desktop version of the same market simultaneously) and the price updating on the mobile interface; median across ten observed price updates; (c) Crash and freeze events — any observed unintentional termination of the mobile session during the test window; (d) Scroll and navigation efficiency — how many taps are required to navigate from the home screen to an in-play tennis market; (e) Font size compliance — whether body text and bet-slip text meet a minimum 16px equivalent for legibility on mobile.

Scoring: Each sub-criterion scored 0–10, mean taken across the five. Touch-target and font-size compliance are binary pass/fail (10 or 0); the remaining three are continuous scales. Crash events result in an automatic −2 per observed event, uncapped.

Composite score calculation

The composite score is the weighted sum of the five axis scores: (axis1 × 0.30) + (axis2 × 0.25) + (axis3 × 0.20) + (axis4 × 0.15) + (axis5 × 0.10). The result is expressed on a 0–10 scale, rounded to one decimal place for display. The composite is then converted to the "x/5" format shown on operator cards by dividing by two: a 9.6 composite becomes 4.8/5. This conversion is purely presentational; the underlying 10-point scale is the working model.

Operator ranking on the home page reflects composite score order. Where two operators are within 0.1 composite points of each other, the tiebreak is applied in order: first, Axis 1 (market depth) score; then Axis 2 (withdrawal throughput). Commission rate is not a tiebreak variable.

For a full breakdown of specific market types covered in the Axis 1 assessment, see tennis-betting-guide.php. For odds format and implied probability context, see odds-on-court.php. To contact the desk about the methodology, use editorial-contact.php.