A dedicated four-digit drawer for raffles, table IDs, and teaching demos. Pick how many codes to reveal each round—processing stays in your browser, with guidance on when not to treat outputs as real PINs.
This page exists for one job: produce random four-digit numbers without asking you to configure min/max ranges first. Four-digit codes appear in raffle tickets, classroom table IDs, quiz labels, story locker combinations, and disposable demo values. When you already know the length must be four, a focused page is clearer than a general number form.
Every draw runs in your browser on ODLUCK. Choose how many numbers to show in a round, generate, then read them aloud, write them on a board, or copy them into notes. There is no account gate. Independent clicks can repeat a number—the same way a fair raffle can—because each draw does not “remember” to exclude previous winners unless you track that yourself.
This is not a password vault and not a banking PIN locker. For secrets that need letters and symbols, use the 12-character password generator. For lengths other than four, use the N-digit generator (including ?digits= links). Keep this bookmark when your workflow is specifically four digits so hosts and teachers do not re-explain a flexible form every time.
No numbers drawn yet — set length and count, then generate your first codes.
A facilitator playbook unique to this fixed four-digit page—different from the N-digit length ladder and from password signup checklists.
Before opening ODLUCK, check that printed stubs, QR codes, or signup sheets all use four-digit IDs. If some tickets are six digits, switch to the N-digit tool instead of improvising mid-draw.
Show the generator on a shared screen. One code per round keeps the room focused. Use higher counts only when assigning several tables at once—not for a single grand prize.
Transparency is the product. Narrate the click, read the four digits slowly, and pause for matches. Avoid regenerating silently if nobody answers on the first try unless your rules allow a redraw.
Write claimed codes on a visible list so repeats are handled consciously. Generate again only after the previous match is settled. Never photograph a “temporary PIN” into a public chat as if it were a banking secret.
Set the count, generate on a visible screen when fairness matters, then reuse for as many rounds as the activity needs.
Pick how many 4-digit numbers to reveal (commonly 1–4). One number suits a single winner; several numbers help when comparing samples or assigning multiple tables at once.
Click generate to produce a fresh set. For raffles and classroom demos, project or pass the phone so participants watch the click—transparency is part of the product use case.
Write results down if the activity needs a lasting list. Generate again for the next round. Do not photograph a “temporary PIN” into a public chat if anyone might reuse it as a real secret.
Stay here for fixed-width raffle codes; switch only when length or character set requirements change.
One flexible page for 2–12 digit lengths when four digits are not enough (supports ?digits=).
Create stronger secrets with letters, numbers, and symbols—not digit-only codes.
Build letter labels or mix letters with digits offline for grouping codes.
A four-digit code has a small search space. That is fine for raffles and classroom demos; it is unacceptable as a long-term bank, email, or phone unlock secret—especially after it appeared on a projector.
If your real need is a signup password, leave this page and use the 12-character password generator with mixed character classes, then store the value in a password manager. Keep four-digit draws for games only.
Independent draws do not automatically exclude previous winners—just like physical raffle tickets drawn with replacement unless you remove them.
If your rules require unique winners, maintain a claimed-code list and regenerate until you get an unused value. Explaining that policy aloud before the first click prevents arguments when a repeat appears.