Crash hub
Crash-style multiplier games with a stated loss cap.
Decision rule
Read a crash app before install when the reader wants a multiplier-curve game with a clear loss cap and a stated auto-cash-out.
What separates two apps in this category
Read the auto-cash-out default and the loss cap. Two crash apps that share a curve can still differ on the cap.
Crash-style apps are not the same as slot apps even though the multiplier curve looks similar. The reader chooses when to cash out before the round resolves, which means the per-round decision is on the reader's side, not on the developer's. The directory surface treats the round-log retention and the auto-cash-out default as the cleanest two signals.
The directory treats crash-style multiplier games as one decision-rule family. Empty sub-families are not published. The cards below cover the entries we have read on the developer page. New entries appear here as soon as the changelog is verified and the developer page is opened.
Editorial
The five sections below cover the editorial reading order: what the category is, how to read a version note, how to read the round surface, how to read the responsible-use surface, and how to choose an entry.
The crash round resolves when the multiplier line crashes. The reader chooses when to cash out. The slot round resolves when the reels stop. The difference is on the reader's side: in a crash round the per-round decision is real and frequent; in a slot round it is mostly a tap.
A crash curve is published as either a probability table (p(m) for each m) or a histogram of past round results. The two are not the same. A probability table is the developer's claim about the long-run distribution. A histogram of past rounds is a sample of the actual outcomes. A reader who wants to verify the curve should compare the two; a reader who has only the histogram should treat the curve as a sample, not a contract.
The version bumps that change the most on crash apps are curve-shape changes and round-log cap changes. A version that raises the round-log cap from 50 to 500 is a verification-positive change. A version that adjusts the curve shape is a verification-rebuild change. A version that only renames a screen is neither.
Round history is the only verification surface after the fact. An app that exports a signed round log lets the reader verify the curve against the developer-claimed shape. An app that retains the last 50 rounds does not. The directory lists retention where the developer publishes it; elsewhere the entry reads "not published".
Auto-cash-out configuration is the cleanest second signal after the loss cap. Where the developer publishes a default value, the entry lists it. Where the developer is silent, the entry reads "not published". The session-length reminder is surfaced where the developer has one.
Choose when the reader wants a stated auto-cash-out config and a visible round log. Avoid if the loss cap is missing.
What separates two apps in this category
The single biggest difference is whether the round log exports. Apps that do not export logs cannot be re-checked later by the reader.
14 entries indexed. The cards below cover the entries we have read on the developer page. New entries will appear here as soon as the changelog is verified.
Comparison table
The table is short on purpose. We compare only the fields the developer page has actually published.
| App | Version | Android | First seen | Score | Verified |
|---|---|---|---|---|---|
| Crash Cloud 99 | v3.2.0 |
8.0+ | Feb 2025 | 4.0 | Verified |
Entries