reportingrisk.com← the monitorSEC reporting failures, scored and checked against what happened next

Or browse all companies A–Z.

Rubicon Technologies, Inc.

No reporting failures in the last 12 months

It filed on time and stood behind its numbers. Of companies scoring zero, 4.0% were delisted, went bankrupt, restated or stopped filing within the following year.

$64Mstalepublic float
2024-11-14most recent failure
2025-01-22delisted or deregistered
2024-05-17declared past accounts unreliable

Score over time

024202220232024202520262022-10-01 · score 12022-08-30 auditor change2023-01-01 · score 22022-11-14 filed late (10-Q) · going concern2022-08-30 auditor change2023-04-01 · score 22022-11-14 filed late (10-Q) · going concern2022-08-30 auditor change2023-07-01 · score 32023-05-15 filed late (10-Q) · liquidity2022-11-14 filed late (10-Q) · going concern2022-08-30 auditor change2023-10-01 · score 22023-05-15 filed late (10-Q) · liquidity2022-11-14 filed late (10-Q) · going concern2024-01-01 · score 12023-05-15 filed late (10-Q) · liquidity2024-04-01 · score 12023-05-15 filed late (10-Q) · liquidity2024-07-01 · score 22024-05-17 accounts unreliable2024-05-15 filed late (10-Q) · accounts not ready2024-10-01 · score 42024-09-24 auditor change2024-08-14 filed late (10-Q) · accounts not ready2024-05-17 accounts unreliable2024-05-15 filed late (10-Q) · accounts not ready2025-01-01 · score 52024-11-14 filed late (10-Q) · accounts not ready2024-09-24 auditor change2024-08-14 filed late (10-Q) · accounts not ready2024-05-17 accounts unreliable2024-05-15 filed late (10-Q) · accounts not ready2025-04-01 · score 52024-11-14 filed late (10-Q) · accounts not ready2024-09-24 auditor change2024-08-14 filed late (10-Q) · accounts not ready2024-05-17 accounts unreliable2024-05-15 filed late (10-Q) · accounts not ready2025-07-01 · score 32024-11-14 filed late (10-Q) · accounts not ready2024-09-24 auditor change2024-08-14 filed late (10-Q) · accounts not ready2025-10-01 · score 12024-11-14 filed late (10-Q) · accounts not ready

Hover or tap a dot to see the filings behind that score.

Why they said they were late

Rubicon Technologies, Inc. (“Rubicon” or the “Company”) is filing this Notification of Late Filing on Form 12b-25 with respect to its Quarterly Report on Form 10-Q for the quarterly period ended September 30, 2024 (the “Quarterly Report”). The Company has determined that it is unable to file its Quarterly Report within the prescribed time period without unreasonable effort or expense due to several recent transactions and related disclosures, thereby requiring the Company to take additional time to complete its financial information as reported on Form 10-Q. The Company intends to file the Quarterly Report within the five-day grace period provided by Rule 12b-25

NT 10-Q, filed 2024-11-14 · accounts not ready

What it filed

2024-11-14filed late (10-Q)accounts not ready SEC →

Rubicon Technologies, Inc. (“Rubicon” or the “Company”) is filing this Notification of Late Filing on Form 12b-25 with respect to its Quarterly Report on Form 10-Q for the quarterly period ended September 30, 2024 (the “Quarterly Report”). The Company has determined that it is unable to file its Quarterly Report within the prescribed time period without unreasonable effort or expense due to several recent transactions and related disclosures, thereby requiring the Company to take additional time to complete its financial information as reported on Form 10-Q. The Company intends to file the Quarterly Report within the five-day grace period provided by Rule 12b-25

2024-09-24auditor changed or resigned SEC →

2024-08-14filed late (10-Q)accounts not ready SEC →

Rubicon Technologies, Inc. (“Rubicon” or the “Company”) is filing this Notification of Late Filing on Form 12b-25 with respect to its Quarterly Report on Form 10-Q for the quarterly period ended June 30, 2024 (the “Quarterly Report”). The Company has determined that it is unable to file its Quarterly Report within the prescribed time period without unreasonable effort or expense due to several recent transactions and related disclosures, thereby requiring the Company to take additional time to complete its financial information as reported on Form 10-Q. The Company intends to file the Quarterly Report within the five-day grace period provided by Rule 12b-25

2024-05-17accounts declared unreliable SEC →

2024-05-15filed late (10-Q)accounts not ready SEC →

Rubicon Technologies, Inc. (“Rubicon” or the “Company”) is filing this Notification of Late Filing on Form 12b-25 with respect to its Quarterly Report on Form 10-Q for the quarterly period ended March 31, 2024 (the “Quarterly Report”). The Company has determined that it is unable to file its Quarterly Report within the prescribed time period without unreasonable effort or expense due to several recent transactions and related disclosures, thereby requiring the Company to take additional time to complete its financial information as reported on Form 10-Q. The Company intends to file the Quarterly Report within the five-day grace period provided by Rule 12b-25

2023-05-15filed late (10-Q)liquidity SEC →

The Quarterly Report on Form 10-Q for the three months ended March 31, 2023 (the “Quarterly Report”) of Rubicon Technologies, Inc. (the “Company”) could not be filed within the prescribed time period without unreasonable effort or expense due to a delay experienced by the Company in completing its disclosures in the Quarterly Report. This delay principally relates to the Company’s ongoing negotiations of potentially material transactions with financing sources to refinance maturing debt and improve the Company’s financial position. Management’s efforts related to negotiating the potential refinancing transactions and evaluating the Company’s financial position, including its liquidity position, have required a significant amount of management’s time and other Company resources that normally would be devoted to the preparation of the Quarterly Report and related matters. The Company intends to file the Quarterly Report within the five-day grace period provided by Rule 12b-25

2022-11-14filed late (10-Q)going concern SEC →

The Quarterly Report on Form 10-Q for the three months ended September 30, 2022 (the “Quarterly Report”) of Rubicon Technologies, Inc. (the “Company”) could not be filed within the prescribed time period without unreasonable effort or expense due to a delay experienced by the Company in completing its disclosures in the Quarterly Report. This delay principally relates to the Company’s ongoing negotiations of potentially material transactions with financing sources to refinance the maturing debt, improve Company’s financial position and for the Company to be able to continue as a going concern for at least the next twelve months. Management’s efforts related to negotiating the potential refinancing transactions and evaluating the Company’s financial position, including its liquidity position, have required a significant amount of management’s time and other Company resources that normally would be devoted to the preparation of the Quarterly Report and related matters. 2

2022-08-30auditor changed or resigned SEC →

About this score

reportingrisk.com scores every active US filer on three things a company tells the SEC about itself: late-filing notices on Form NT, 8-K item 4.02 (past accounts declared unreliable) and 4.01 (auditor changes). 1,012 are flagged today.

Every score is frozen and checked twelve months later. Across 91,452 of them, a company scoring 4 or more ended that year delisted, bankrupt, restated or silent 17.2% of the time, against 4.0% for a clean record. Scores before 2026-09-27 were reconstructed from the filing history as it stood at each date, so the record is a backtest rather than years of live calls.

See the ledger → Every company the score flagged that later failed, what it told the SEC on the way down, and the ones it missed.

Every item above is a filing this company made with the SEC.
Snapshot 2026-11-04 · data from SEC EDGAR (public domain) · not investment advice

reportingrisk.com← back to the monitorAll companies A-Z · RSS · found an error? hello@reportingrisk.com