Practical guide
Consecutive Tarot Card Repeats: A Run Within a Longer Record
Under a uniform 78-identity independent replacement model, the chance of a length-three run somewhere in seven picks is 0.081332%. This differs from all seven matching or any identity repeating. Overlapping candidate windows require a count that avoids double-counting.
Define one run length inside one fixed window
“Three cards in a row were the same” can describe a short streak somewhere inside a longer record. It is different from all cards in the entire record matching, and different from one identity appearing twice with other cards between them. Choose the exact event before attaching a probability.
Let N be the number of distinct equally likely identities, m the total number of picks in the stated window, and r the qualifying consecutive-run length. A run of at least r identical consecutive picks qualifies, including a longer run. Count the window once if it qualifies, even if several starting positions show a streak.
The reference table uses N=78, independent picks and replacement before every pick. Orientation is ignored when defining an identity. This is a hypothetical selection model, not a measured result for a deck, this site’s tool or a person’s record. Returning a card makes it available; uniformity and independence are additional assumptions.
The existing repeated-card guide already calculates next matches, whole-window all-matches and any identity repeat. Its calculator explicitly excludes a shorter streak somewhere inside a longer record. This page supplies that separate calculation.
Keep nonadjacent repeats, whole-window matches and runs separate
In the fictional record A–B–B–C–D–E–F, an identity repeats and a length-two run occurs. No length-three run occurs. In A–B–C–A–D–E–F there is a nonadjacent repeat but no equal adjacent pair. Those records cannot be classified with the same event label.
For one specified block of three independent uniform picks, all three identities match with probability 1/N²: the first can be anything, while the next two must match it. For all seven picks to match each other, the expression is 1/N⁶. Neither expression answers whether some length-three run appears anywhere among seven picks.
Under the stated N=78 model, at least one length-three run somewhere in seven picks has probability 0.081332%. At least one adjacent match in the same seven-pick window has probability 7.449934%. The broader event has more qualifying outcomes. It is not evidence that a particular person should seek a streak.
On a phone, scroll the table sideways. Keyboard users can focus it and use the arrow keys.
| Window m | Run length r or longer | Exact-count result, rounded | Sum-of-window upper bound, rounded |
|---|---|---|---|
| 7 | 2 | 7.449934% | 7.692308% |
| 7 | 3 | 0.081332% | 0.082183% |
| 7 | 4 | 0.000835% | 0.000843% |
| 14 | 2 | 15.442995% | 16.666667% |
| 14 | 3 | 0.194802% | 0.197239% |
| 14 | 4 | 0.002291% | 0.002318% |
| 30 | 2 | 31.215980% | 37.179487% |
| 30 | 3 | 0.453678% | 0.460224% |
| 30 | 4 | 0.005619% | 0.005690% |
The last column is an upper bound formed by adding the individual candidate-window probabilities, capped at one. It is not the exact result. Six decimal places help compare the calculations; they do not establish that an unknown selection process deserves that precision.
See why overlapping windows cannot simply be added
Use a small original two-identity model: each independent pick is A or B with equal probability. Observe four picks and ask whether three consecutive picks match. There are 2⁴ = 16 equally likely ordered records.
A run can start at position one or two. The first window matches in AAAA, AAAB, BBBB and BBBA. The second matches in AAAA, BAAA, BBBB and ABBB. Adding four plus four counts AAAA and BBBB twice.
The union therefore has 4+4−2 = 6 records out of sixteen, or 3/8 = 37.5%. Merely adding two probabilities of 1/4 would incorrectly give 50%. A four-pick run contains two matching three-pick windows but qualifies as one record.
On a phone, scroll the table sideways. Keyboard users can focus it and use the arrow keys.
| Record | Qualifying start positions | Count the record |
|---|---|---|
| AAAA | 1 and 2 | Once |
| AAAB | 1 | Once |
| BAAA | 2 | Once |
| BBBB | 1 and 2 | Once |
| BBBA | 1 | Once |
| ABBB | 2 | Once |
This example shows dependence for the overlapping three-pick windows. It does not imply that every kind of overlap must have the same correction. The reference result below uses a prefix count that handles any qualifying run without having to label all its overlapping windows.
Count prefixes that have not yet reached the run
For a length-three event, keep two safe states. State one counts records whose final run has length one; state two counts records whose final run has length two. Neither state has already contained a length-three run anywhere. Records that hit the event leave these safe states.
After one pick there are N safe records in state one and zero in state two. From either safe state, N−1 different identities break the final run and return to state one. The one same identity extends state one to state two. A same-identity extension from state two hits length three, so it is excluded from the safe count.
Safe final run: 1
A different identity returns to state 1; the same identity moves to state 2.
Safe final run: 2
A different identity returns to state 1; the same identity reaches the event.
Already hit the event
Do not include this prefix in either safe state. Count the event by subtracting all safe records from all possible records.
If the current safe counts are a₁ and a₂, the next counts are new a₁ = (N−1)(a₁+a₂) and new a₂ = a₁. Both new values use the previous counts; do not update a₁ and then use that new value for a₂.
For N=2 the states after one, two, three and four picks are (2,0), (2,2), (4,2) and (6,4). Ten four-pick records avoid the run, so sixteen minus ten gives the six qualifying records listed above.
For general r, keep safe states for final run lengths one through r−1. Different identities reset to state one; a same identity extends a safe run by one, unless it reaches r. After m picks, subtract the sum of safe states from Nᵐ and divide by Nᵐ.
The displayed results were calculated with exact integer counts and checked independently by listing all ordered records in several small models. The calculation is not a simulation or a sample of actual tarot draws.
Use the simpler adjacent-match formula and keep the limits visible
For r=2, a record avoids the event only when every new identity differs from the preceding one. The first has N choices, and each later pick has N−1 choices. Thus the no-adjacent-match probability is (1−1/N)ᵐ⁻¹, and its complement is 1−(1−1/N)ᵐ⁻¹. This agrees with the safe-prefix count.
For seven picks and N=78, use 1−(77/78)⁶ = 7.449934%. This is the chance of at least one adjacent match anywhere in the fixed window. The chance that just the next pick matches a known preceding identity remains 1/78. A longer window supplies more opportunities, not a different next-pick probability.
If unique physical cards stay out without replacement, that physical identity cannot form a repeat run in that block. Duplicate printed names, unequal selection weights or changing pools need their own actual inputs. Do not change N alone and pretend a weighted-name model became uniform.
Choose the window and event before looking at the record if you want this comparison. If you already saw a qualifying run, the event is known to have occurred; this table is not the chance that the recorded fact is true. An incomplete or retrospectively selected history cannot be assigned the reference percentage without further information.
A small model probability does not identify a cause, validate a prediction or create an obligation to continue drawing. An optional creative association can remain separate from the observation. Stop when the counting question is clear.
Download the blank consecutive-run record
Read the original safe-prefix counting notes
Both are plain-text files for a bounded study task, with no submission or scoring step. The notes state the recurrence and complete sixteen-outcome counterexample.
Check four complete run questions
These original examples test the event definition and the counting procedure. They do not grade intuition or recommend a number of draws.
Case 1
The seven-pick record is A–B–B–C–D–E–F. Does it contain a qualifying run for r=3?
Show answer and explanation for case 1
No. Its longest consecutive equal-identity run has length two.
B appears twice and the pair is adjacent, so the record qualifies for r=2. It does not qualify for r=3. Counting any repeat or any adjacent pair would answer a broader question.
Case 2
In the A/B four-pick example, AAAA qualifies at two starting positions. Should it contribute two to the probability numerator?
Show answer and explanation for case 2
No. The event concerns qualifying records, so AAAA contributes once.
There are sixteen records. Six qualify for a run of at least three. Adding the two four-record window lists double-counts AAAA and BBBB; subtract their intersection to obtain six, not eight.
Case 3
You already observed A–A–A at the start of a seven-pick record. Is 0.081332% the chance that this record contains a length-three run?
Show answer and explanation for case 3
No. The qualifying run is already observed.
The reference percentage describes a seven-pick window before observing its outcomes under the stated model. Once the first three equal picks are known, this particular record already satisfies the event. Keep that observation separate from a question about future picks or an interpretation.
Case 4
For the N=2 length-three recurrence, the old counts are (4,2). What are the next safe counts, and why is updating them in place unsafe?
Show answer and explanation for case 4
The next counts are (6,4). Both use the old values.
New state one is (2−1)(4+2)=6; new state two is the old state-one count 4. Using the newly calculated 6 for state two would produce (6,6), giving twelve safe records instead of ten. Both updates must use the previous pair of counts.
Sources and further reading
- Tarot Tools: complete repeated-card event guideExisting rule definitions distinguish next matches, fixed-block all-matches and any repeat. Its calculator excludes shorter streaks inside longer windows.
- Original safe-prefix counting notes and complete small exampleOriginal derivation and explicit finite-outcome check for this article. A mathematical model explanation, not an independent shuffle audit or prediction study.