Robinhood’s two Rule 606 totals describe one revenue stream—not $978 million

A public filing can be perfectly accurate and still be easy to misread when two affiliated companies report different stages of the same revenue stream. That is the problem presented by Robinhood’s third-quarter 2026 Rule 606 disclosures. An aggregation of the figures for Robinhood Securities LLC and Robinhood Financial LLC produces an apparent $977.8 million of order-routing remuneration. The arithmetic is correct. The economic conclusion is not. Robinhood’s own intercompany disclosure says Robinhood Securities passes 80% of specified market-centre revenue to Robinhood Financial. The Q3 numbers reproduce that relationship with near-exact precision: $434,592,966.65 is 79.999999993% of $543,241,208.36. The smaller figure is therefore not an independent second pot of revenue that can be added to the first.[1][2][3]

The distinction matters because Rule 606 data are increasingly being repackaged into rankings, dashboards and comparisons. A database that treats each broker-dealer filing as a standalone economic total can count the same underlying remuneration twice when affiliated entities disclose both receipt and allocation. For Robinhood, the defensible Q3 measure is the $543.2 million reported at Robinhood Securities, the routing and clearing broker that receives venue payments. Robinhood Financial’s $434.6 million is analytically useful—it shows the internal division of the revenue—but it should not enlarge the group total.[1][2][3][4]

A separate $114.2 million at Webull

Webull Financial LLC reported $114,229,124.56 of net payment for order flow and execution rebates for Q3 2026 in the same extraction framework. Unlike the Robinhood affiliate pair, Webull is a separate firm and its amount can be added without duplicating Robinhood’s chain. The resulting two-firm direct-filer measure is $657,470,332.92: $543.2 million from Robinhood Securities and $114.2 million from Webull Financial. Robinhood accounts for 82.63% of that sum and Webull 17.37%. This is not a measure of the whole US retail-brokerage market; it is a deliberately bounded comparison of two filings examined here.[1][5][6]

The filing archive is important because the Rule 606 system is not an income statement. It records order-routing information by security type, order type and market centre, including the net payments or rebates associated with disclosed routes. Route shares are usually expressed by order count, while remuneration may be reported using rates tied to shares or contracts. A firm’s total in a third-party extraction is therefore a reconstruction from the underlying structured disclosure, not a line item labelled “PFOF revenue” in audited group accounts. FXBrokers.ai used the public extraction to aggregate the structured values and checked the filing identities and quarter against the firms’ official disclosure libraries.[1][2][5][4][6][7]

The quarter grew, but not for a single simple reason

Robinhood Securities’ extracted total rose from $498,436,716.44 in Q2 to $543,241,208.36 in Q3, an increase of $44.8 million or 8.99%. That movement should not be described as a pure rise in equity payment for order flow. The Rule 606 total spans disclosed routing arrangements, and Robinhood’s consolidated accounts show that transaction economics differed markedly by product. In the third quarter, Robinhood reported $399 million of options transaction-based revenue, $121 million from equities, $120 million from cryptocurrencies, $173 million from event contracts and $54 million from other sources. Total transaction-based revenue was $867 million.[8][1]

The company’s explanation also shows why volume and revenue can move in different directions. Options contracts traded per trader increased 66% from the year-earlier quarter even though the number of users placing options trades fell 11%. Robinhood said the benefit was partly offset by lower option rebate rates caused by the mix of ticker symbols traded. Equities revenue rose as average notional volume per trader increased 48%, again partly offset by lower rebate rates arising from ticker mix. Those statements do not prove that every additional Rule 606 dollar came from more customer activity; they show that activity, product mix, security mix and rate schedules all mattered.[8]

There is another boundary that prevents the $657.5 million comparison from being mistaken for consolidated revenue. Robinhood’s $867 million transaction-based revenue includes event contracts, cryptocurrencies and other items that are not equivalent to the securities-routing remuneration reconstructed from Rule 606. Conversely, Rule 606 can capture venue payments in a level of route detail that does not map one-for-one onto the public company’s segment labels. The two datasets illuminate different questions. The 10-Q measures recognised group revenue under accounting rules. The routing disclosure describes where specified customer orders went and what the broker-dealer received from market centres.[8][4]

Why the 80% relationship is the decisive test

The best protection against double counting is not an assumption about corporate names; it is an explicit mapping of the legal entities and the payment chain. Robinhood’s disclosed arrangement says Robinhood Securities receives market-centre revenue and passes 80% of specified revenue to Robinhood Financial. Applying 80% to the Q3 Robinhood Securities total gives $434,592,966.688. The reported Robinhood Financial figure is $434,592,966.65, a difference of four cents after rounding across a total exceeding $434 million. The match is stronger than a loose correlation. It is an internal-consistency test that explains the two filings.[1][2][3]

That does not make the Robinhood Financial disclosure redundant. It answers a different question: how much of the routing remuneration moves to the customer-facing affiliate under the intercompany arrangement. Analysts can use the pair to examine the allocation, compare it over time and test whether the stated percentage continues to hold. What they cannot responsibly do is add both figures and call the result Robinhood’s PFOF. An apparent $977.8 million would overstate the economic stream by $434.6 million, or 80% of the amount received by Robinhood Securities.[1][2][3]

The same discipline should be applied across the market. Introducing brokers, clearing brokers and affiliated executing entities can each have reporting responsibilities depending on who makes routing decisions and how orders are handled. The SEC’s Rule 606 guidance addresses those responsibilities, but a public filing index does not itself tell a downstream user which numbers represent independent economic flows. A robust market-wide comparison needs a legal-entity map, a route-decision map and an intercompany-payment map before it sums anything.[4]

What this investigation establishes—and what it does not

This analysis establishes three things. First, Robinhood’s Q3 affiliate totals are linked by the disclosed 80% pass-through and should not be added as independent revenue. Second, Robinhood Securities’ extracted Q3 total increased 8.99% from Q2. Third, adding the separate Webull filing produces a bounded two-firm figure of $657.47 million. It does not establish customer harm, inferior execution or a breach of best-execution obligations. Payment for order flow creates an economic conflict that firms and regulators must supervise, but the existence or size of a payment is not, by itself, proof that a customer received a worse execution.[8][1][2][5][3][4]

Nor does the analysis endorse every conclusion generated by the third-party execution-report platform. Its aggregate remuneration values are useful extractions from public structured filings; its execution-quality flags involve additional methodology and peer benchmarking that are outside this article’s calculation. The load-bearing finding here is independently reproducible from the disclosed totals and Robinhood’s documented 80% allocation. The practical lesson is narrower and more important: in broker data, entity-level transparency can create group-level double counting unless the analyst reconstructs the commercial relationship first.[1][2][5][3]

A reproducible method for group-level comparisons

A dependable aggregation process should begin with the legal filer, not the consumer brand. For each filing, record the broker-dealer CRD identity, the entity that accepted the customer order, the entity that made the routing decision, the market centre that paid or charged remuneration, and any disclosed transfer among affiliates. Only after those relationships are mapped should the amounts be grouped at brand or parent level.[3][4]

The process also needs a quarter-consistency check. A data service may update one affiliate before another, or a firm may amend a report. Summing files from different periods can create an apparent movement that never occurred. Here, all three direct-filer figures used for the central comparison are labelled Q3 2026, and Robinhood’s Q2 figure is used only for the separate quarter-on-quarter calculation.[1][2][5]

A third check is unit consistency. Route reports can state remuneration per share, per contract or as total dollar amounts, and the security categories differ. An analyst should not compare a per-contract options rate with a per-share equity rate or infer group revenue by multiplying a rate against an incompatible volume field. The aggregate values used here come from one extraction method within each filing, and the independent 80% pass-through test confirms the Robinhood relationship without inventing a cross-unit conversion.[1][2][5][3][4]

What a market-wide total would still require

This two-firm analysis cannot be extrapolated into an industry market share. Other large retail brokers use different business models: some receive venue remuneration, some internalise through affiliated market makers, some route without retaining PFOF, and some combine commission, spread, interest and lending income. Their Rule 606 files may also allocate responsibilities across introducing and clearing entities differently. A complete total would need every relevant filer, a policy for affiliated flows and controls for amendments and missing reports.[4]

The exercise nevertheless exposes a material methodological risk for any future ranking. Robinhood’s affiliated disclosures alone can inflate an aggregate by $434.6 million if treated as independent. At the two-firm scale, that error would turn the defensible $657.5 million combined figure into $1.092 billion—a 66.10% overstatement. The percentage is calculated as the duplicated $434.6 million divided by the correct $657.5 million total.[1][2][5][3]

That is why this finding matters beyond Robinhood. Transparency rules often produce multiple accurate records around one economic chain. The analyst’s job is not merely to download and add them; it is to understand what each entity did. A future public dashboard should show gross venue receipts, intercompany allocations and consolidated non-duplicated totals as separate fields. That would preserve the value of both filings while preventing a ranking error from becoming a false headline.[1][2][3][4]

Revenue recognition is another reason not to transplant the figure

The Rule 606 remuneration total also should not be inserted into Robinhood’s income statement as if it were an audited line. The reporting periods align, but accounting recognition can include accruals, contra-revenue, affiliate eliminations and products outside Rule 606. Robinhood’s consolidated filing is the authoritative source for group revenue; the route report is the authoritative source for the disclosed routing relationships. Reconciliation is a research question, not an assumption.[8][1][2][4]

For analysts, the clean output is therefore a three-column bridge: market-centre remuneration received by the routing entity, intercompany allocation to the introducing entity, and consolidated transaction-based revenue reported by the parent. Keeping those columns separate prevents both double counting and false claims that an extracted route total must equal a GAAP revenue category.[8][1][2][3]

Report an error or submit an update