Maths Is Fun Divisibility Rules

Why These Rules Actually Matter

Divisibility rules are shortcuts for testing whether a number can be divided evenly by another without actually doing the long division. Most people learn the ones for 2, 5, and 10 in elementary school and then never touch the subject again. The rest get skipped because the curriculum moves on. But if you work with numbers regularly — auditing, accounting, any field where you scan large spreadsheets — knowing these rules saves you from running a calculator through half your dataset. The Maths Is Fun Divisibility Rules page is one of the cleaner reference resources out there for this. It lays them all out in a straightforward format without padding. I've used it as a quick check when someone hands me a list of invoice numbers and asks which ones are divisible by 7 or 13. Rather than run a formula across every cell, I apply the rule mentally and flag the ones that fall through.

The Basics (You Probably Know Half of These)

Maths Is Fun Divisibility Rules — What They Actually Cover

Here is the quick rundown, starting with the ones everyone learns and moving into the less common territory where things get interesting. Rule for 2: The last digit is even. That's it. Zero, two, four, six, or eight at the end and the number is divisible by 2. No calculation needed. Rule for 3: Add up all the digits. If the sum is divisible by 3, the original number is too. Example: 276. Two plus seven is nine, nine plus six is fifteen, fifteen divides by three evenly, so 276 does too.

Rule for 4: Look at the last two digits. If that two-digit number is divisible by 4, the whole thing is. 1,352 — last two digits are 52, and 52 divided by 4 is 13. Works every time. Rule for 5: Last digit is zero or five. This one needs no explanation really. Rule for 6: It has to pass both the rule for 2 and the rule for 3. Even last digit, and the digit sum divisible by three. If either condition fails, the number fails.

Rule for 9: Same logic as the rule for 3, but the digit sum has to be divisible by 9 instead. A useful side note: the digit sum of a number divisible by 9 will itself always reduce to 9 if you keep adding digits until you get a single digit. Not true for 3. Rule for 10: Ends in zero. Again, obvious.

Where It Gets Less Obvious

Rule for 8: Check the last three digits. If that three-digit chunk is divisible by 8, you're good. This one trips people up because most stop at checking the last two digits like they do for 4. Rule for 11: Alternating sum of digits. Add the first digit, subtract the second, add the third, subtract the fourth, and so on. If the result is divisible by 11 (including zero), the original number is too. Example: 2,973. Two minus nine is negative seven, negative seven plus seven is zero, zero minus three is negative three. Not divisible by 11. Quick check confirms it. Rule for 7: Double the last digit and subtract it from the remaining leading truncated number. Repeat if needed. This is the one most people struggle with because it feels unintuitive. Take 203. Double the three to get six. Subtract that from twenty to get fourteen. Fourteen is divisible by seven. Done.

Take a harder one like 637. Double the seven to get fourteen. Subtract fourteen from sixty-three to get forty-nine. Forty-nine divided by seven is seven. Good. Rule for 12: Passes both 3 and 4. That's all there is to it. Some sources don't even list this separately because it's just a combo rule.

Advanced Rules: 13, 17, and 19

These come up far less often in practice but show up in competitive math contexts and occasionally in coding interviews. The pattern is the same as the 7 rule — manipulate the trailing digit and recurse on the remainder. Rule for 13: Add four times the last digit to the remaining leading number. So for 507, four times seven is twenty-eight, add that to five to get thirty-three. Thirty-three isn't divisible by thirteen, so 507 isn't either. Wait, let me recheck. Five hundred seven divided by thirteen is thirty-nine exactly. My arithmetic was off. Four times seven is twenty-eight, plus five is thirty-three. Thirty-three divided by thirteen is not clean. Let me recalculate the actual division. 13 times 39 is 507. So 507 is divisible by 13. But 33 is not. Something is wrong with my application. Actually, I see the issue — the rule works but I applied it wrong. Let me try again properly. For 507: take the last digit 7, multiply by 4 to get 28, add to 50 to get 78. 78 divided by 13 is 6. Correct. I made an arithmetic error there by using 5 instead of 50 as the truncated portion. That's exactly the kind of mistake I mentioned earlier.

Rule for 17: Subtract five times the last digit from the remaining leading number. 374. Last digit is four, five times four is twenty. Thirty-seven minus twenty is seventeen. Divisible by seventeen. It works. Rule for 19: Add two times the last digit to the remaining leading number. 437. Last digit seven, times two is fourteen, add to forty-three to get fifty-seven. Fifty-seven divided by nineteen is three. Clean.

A Practical Edge Case I Ran Into

Last year I was reconciling a batch of transaction codes and needed to verify which ones were divisible by 13. The dataset had over four thousand entries. Running a VLOOKUP or MOD formula on every row was tedious and slowed things down. I wrote out the divisibility-by-13 rule on a scrap of paper and started applying it to groups of entries. The problem came when I hit numbers like 10,001. Truncating that and applying the rule mentally is awkward because the leading portion still looks huge. I kept second-guessing myself on whether I'd doubled or quadrupled the last digit correctly. The workaround was to combine rules strategically. I knew 10,001 isn't divisible by 3 or 7, and since 13 times 769 equals 10,001, it IS divisible by 13. But getting there by mental calculation alone was unreliable. What actually worked was cross-referencing with the rule for 7 first. If a number wasn't divisible by 7 or 11, the odds of it being divisible by 13 dropped significantly, so I could skip most of them. I ended up only running the full divisibility check on about a third of the entries, which cut my processing time from roughly 45 minutes down to maybe 12.

Common Pitfalls and Where These Rules Break

The biggest issue people run into is applying the rule partially and stopping early. For the 7 and 13 rules especially, you may need to repeat the process two or three times before you reach a number small enough to recognize. If you stop after the first iteration and the intermediate result still looks complicated, don't assume it fails — just run it again. Another frequent error is mixing up the multiplier. Seven uses doubling and subtracting. Thirteen uses quadrupling and adding. Seventeen uses quintupling and subtracting. Nineteen uses doubling and adding. These are easy to mix up under pressure, and once you flip a plus to a minus, your answer is wrong and you have no way to catch it without going back. The rules also become practically useless for very large numbers where mental truncation gets error-prone. I've seen people try to apply the rule for 11 to an eight-digit number and lose track of whether they should be adding or subtracting the fifth digit. At that point, just doing the division or running a spreadsheet check is faster than fighting with the rule.

There's also a hard limit on efficiency. The rule for 3 and 9 only works because of how modular arithmetic behaves with base 10. That property doesn't extend cleanly to primes above 19. You can derive rules for 23, 29, 31, and so on using the same recursive technique, but the multipliers get unwieldy and the cognitive load makes the shortcut slower than just dividing. Nobody needs a divisibility rule for 31 in real life.

When to Use These and When to Move On

Use divisibility rules when you need a quick sanity check on a small set of numbers, when you're working without a calculator or spreadsheet, or when you're verifying someone else's work by hand. They are genuinely useful for competitive exams, interview screenings, and field work where computational tools aren't available. Don't use them when you're processing thousands of records, when the numbers have more than six digits, or when you're already sitting at a computer with formula capability. The mental overhead of applying the recursive rule to a nine-digit number is almost always greater than just hitting divide. The rule is a shortcut for humans, not a replacement for computation. The Maths Is Fun Divisibility Rules page is worth keeping bookmarked as a reference. It covers the standard set clearly and links to related content on prime factorization and modular arithmetic if you want to understand why these rules actually work rather than just memorizing them. Understanding the underlying math — that 10 3 mod 7, or that 10 -1 mod 11 — makes it easier to derive and remember the rules instead of relying on rote recall, which tends to fail under stress.