A 24 game solver with decimals works by accepting four whole numbers between 1 and 99, then using exact fraction arithmetic internally to find every way to combine them into 24 using only addition, subtraction, multiplication, division, and parentheses. The phrase "with decimals" usually describes a puzzle variant that allows non-integer starting values, but this particular solver keeps the standard rule set—four whole numbers used once each—and produces the decimal-valued intermediate results that many hands genuinely require. Because it represents every intermediate term as a reduced fraction with an integer numerator and a positive integer denominator, it can return solutions like 8 ÷ (3 − 8 ÷ 3) = 24, where 8 ÷ 3 produces the repeating decimal 2.666… and the inner subtraction yields exactly 1/3. A solver that only tests integer arithmetic would silently reject the hand 3, 3, 8, 8 and report "no solution," missing a valid construction. The fraction-based approach also avoids binary floating-point rounding errors: a value like 0.1 never appears as 0.0999999, so the final check (numerator = 24 × denominator) stays reliable even on hands with long repeating decimals. This makes the tool useful for both standard card puzzles and the decimal-flavoured 24 Game editions sold for grades 5 and up.
What a 24 Game Solver With Decimals Actually Means
The 24 Game, as documented by the UC Santa Cruz MBAMP mathematics program, is a long-running arithmetic puzzle: take four given numbers, use each exactly once, and combine them with +, −, ×, ÷, and parentheses to reach exactly 24. Different commercial editions adjust the input range and rule set, and a "Fractions/Decimals" edition allows starting values that include non-integers. This 24 Game Solver deliberately accepts positive whole numbers through 99 while keeping the standard operation contract, which is broader than any single card pack. Inside the page, "with decimals" describes how the answers behave rather than the form of the inputs: hands such as 3, 3, 8, 8 need a fractional intermediate to reach 24, and the solver returns that fraction without rounding or floating-point comparison noise.
Solve a 24 Game Hand in Three Steps
- Enter exactly four whole numbers, one per field. Each value must lie between 1 and 99 inclusive. Decimals like 1.5, negative numbers like −3, and zero are not accepted by the input contract—paste the puzzle exactly as written or as the cards show.
- Select Solve to exhaustively search the allowed arithmetic operations with exact fractions. The solver tries every legal pairing, both subtraction orders, and both non-zero division orders at every step, returning the new term to the pool until only one number remains.
- Read each returned expression from inside the parentheses outward, then confirm it ends with "= 24." If the page shows no solution, the exhaustive search under the disclosed rules and input bounds returned nothing; treat that as the verdict for this hand rather than a tool error.
Why Fraction Math Catches Decimal-Style Answers
The hand 3, 3, 8, 8 illustrates why a fraction-based solver exists. A natural-looking attempt is (3 + 3 ÷ 8) × 8, but 3 + 3/8 = 27/8, and 27/8 × 8 = 27, not 24. Integer-only checkers also reject 8 × (3 + 3 ÷ 8) for the same reason. The actual solution, 8 ÷ (3 − 8 ÷ 3) = 24, needs the fraction 8/3 inside an inner pair before the outer division. Step by step:
- 8 ÷ 3 = 8/3
- 3 − 8/3 = 9/3 − 8/3 = 1/3
- 8 ÷ (1/3) = 8 × 3/1 = 24
A solver that only compares doubles would compute 3 − 8/3 as 3 − 2.6666666666666665, then divide 8 by that, and report a value such as 23.9999… rather than exactly 24. Other hands such as 1, 5, 5, 5 also rely on a fractional intermediate to reach 24. At each step the solver selects every unordered pair from the remaining terms, combines the pair with + and ×, both subtraction orders, and every legal division order, then folds the new term back into the pool. Repeating that step walks through different pairings and parenthesis structures until only one term remains; this is the pair-and-combine method at work. The solver avoids the floating-point class of bug by representing every intermediate term as a reduced pair with an integer numerator and a positive integer denominator, already cancelled by their greatest common divisor. The terminal check is the integer equation numerator = 24 × denominator, so a value merely close to 24 is never reported as exact, and a path that goes through a long repeating fraction is not lost to rounding. With four inputs bounded at 99, intermediate integer products stay well within JavaScript safe-integer limits, so the fraction representation never overflows while the search tree is explored.
Input Rules and What the Solver Does Not Accept
The solver is deliberately constrained. The verified limits are:
| Accepted | Not accepted |
|---|---|
| Four whole numbers between 1 and 99 | Decimal inputs such as 1.5 or 0.75 |
| +, −, ×, ÷, and parentheses | Concatenation, such as joining 1 and 2 to make 12 |
| Each number used exactly once | Reuse of any input value |
| Exact-fraction intermediate results | Exponentiation, factorials, roots |
| 1 to 50 returned expressions per hand | Operations outside the basic four |
The 50-expression cap matters for hands with many valid rearrangements that share the same arithmetic structure. The list is a set of valid constructions rather than a claim to contain one canonical answer per mathematical equivalence class, sorted by length then locale order so shorter, more direct constructions tend to appear first. If a source puzzle allows powers, factorials, concatenation, decimal-point insertion, or repeated use of a single number, the exhaustive search for that variant is not run here, and the solver may report no solution where a more permissive rule set would find one.
Reading the Returned Expressions
Each line in the result list shows the complete expression followed by "= 24". You can copy the expression into a normal calculator or a dedicated fraction calculator and verify the equality yourself; the solver does not need to be trusted blindly. The parentheses in the expression are significant: they disclose the order of operations and should not be removed casually. A construction like 8 ÷ (3 − 8 ÷ 3) and one written 8 ÷ 3 − 8 ÷ 3 evaluate to different numbers because the parentheses control which divisions feed which subtractions.
A practical reading habit is to evaluate from the innermost parentheses outward. Locate the deepest pair of parentheses, simplify it to a single value, then move outward one level at a time. By the time the outermost parentheses collapse, the result must equal 24, and the equality at the end of the line confirms that the solver's own reduction agreed with your reading.
If the solver reports no solution, double-check that the four numbers were entered in the order they appear on the cards or in the puzzle source. Order does not affect the search—every permutation is tried—but a typo, a leading zero, or a digit transposition will cause the search to run on a different hand and may legitimately return no solution.
When the Solver Returns No Solution
A no-solution result means the exhaustive search found no exact 24 using only addition, subtraction, multiplication, division, parentheses, and each input once under the disclosed rules and input bounds. It is not a software failure. The hand 1, 5, 11, 13 is a documented anchor: under the basic four-operation rules, this hand has no answer, and the solver reliably confirms that. Several other patterns also return no solution, including hands whose numbers do not share enough common factors to reach 24 through the basic operations.
Before treating "no solution" as final, confirm the following:
- All four numbers are between 1 and 99.
- No digit was transposed and no leading zero was added.
- The source puzzle uses the same rule set as this solver—basic operations only, each number once.
- The puzzle does not allow concatenation, exponentiation, factorials, or decimal-point insertion, because those variants can produce answers that this solver will not show.
For classroom or puzzle practice, try the hand on paper first, then select Solve and compare your answer to what the page returns. If a construction matches one of the lines, the result is exact; if the page shows constructions you missed, those become study notes for the next hand. All processing happens in the browser, the four numbers and the generated expressions are not uploaded or stored, and no login is required.