RNGdle Number Rarity Checker

The checker uses the same rule function as this site’s ranking and sandbox. You can enter a number you rolled elsewhere, or choose one you are curious about. The result shows every matching badge, including badges that are earned but do not add to EP because a stronger badge from their family wins. The complete range includes both endpoints, zero and one million.

RNGdle assigns a badge when a number satisfies a numerical or digit-pattern condition. Some conditions inspect the whole integer, such as divisibility, primality, a perfect power, or a Fibonacci value. Others inspect its decimal form: repeated blocks, mirrored ends, alternating parity, digit sums, and sequences that appear inside a longer number. A single roll can satisfy many conditions at once. A number with a simple surface can be surprisingly dense underneath; 420420, for example, matches 21 badges in the frozen public evidence.

EP is the sum of fixed badge values after family selection. Each badge’s value belongs to the captured rules, so this site uses those values directly. A family groups related achievements. If several badges from one family match, the highest-valued match contributes to EP and the other matches remain visible as earned badges. This matters for 420420: BOTANIST matches its digits, but HOTBOX belongs to the same family and has the higher fixed value. The checker marks BOTANIST as not counted while still displaying it. Badges without a family contribute separately.

This distinction explains why adding every badge displayed on a card can produce a number larger than its official EP. Display and scoring answer different questions: which conditions were met, and which of the met conditions contribute after grouping. The 420420 sample has 17 scoring badges out of 21 earned. Its final score is 100,133,055 EP. We use that frozen API record as a regression case, then compare an entire frozen public leaderboard against the local rule implementation one row at a time.

A number’s tier is based on its EP standing among all possible rolls, not a ranking of players. The captured rule table covers 1,000,001 integers and has 60,392 distinct total scores. These totals repeat: dividing the number of integers by the number of reachable EP values gives an average of 16.559 numbers per EP value. That average does not mean every score is shared equally. Some EP totals are common, while the very highest total is reached by one number.

Seven labels describe the number card: trash, common, uncommon, rare, epic, anomaly, and mythic. The labels follow percentile bands in the finite number domain. They do not say how many people have rolled a number, and they do not adjust when a leaderboard changes. The underlying badge scores and family choices determine EP first; the EP determines a position in the all-number distribution; that position determines the card tier. The separate rarity page shows exact EP boundaries and how many numbers fall into each tier.

The same number therefore keeps the same EP under this captured rule version even when different players encounter it. A future game update could alter badge definitions or scores; the date and frozen evidence in this repository make the version being reproduced explicit. Treat the value as a calculation against these recorded rules, not as a promise about an unknown future version.

For a roll you already have, start with the checker above. It gives an immediate EP total and a complete badge list, including which badges score. To understand the full theoretical landscape, read the rarity ranking. That page calculates the top numbers across the entire possible range, rather than drawing conclusions from a day of player activity. It also offers compressed CSV files for independent analysis.

The today page serves a different purpose. It shows a saved public leaderboard snapshot of numbers that players actually rolled on one UTC day. A snapshot has its own capture timestamp; it is not a prediction of the next number and should not be mistaken for a continuously updating feed. When a capture fails, the last successful snapshot keeps its original date. Reading that date is part of reading the table accurately.

If you want to explore without using the original game’s daily chance, the sandbox draws locally with the browser’s cryptographic random generator. It has no account or daily quota and does not contact the original site when you press its button. The badge catalogue places all 233 captured badges in one searchable HTML table. That makes it easier to inspect a condition or family without generating a separate page for every badge.

RNGdle.fun is an unofficial reference and tool site. It does not reproduce the original game’s interface, artwork, or application code. The numerical predicates here were written independently from a documented behavior specification and checked against captured public results. One frozen public record for 420420, a complete 100-entry public day board, targeted predicate examples, and a full-domain comparison anchor the current implementation. These checks let us say what this version computes, while keeping uncertain behavior out of the site.

The original game limits its daily roll according to its own rules. This site cannot grant extra official rolls, alter an account, or submit a score to that game. Its calculator and sandbox work on numbers locally. The number range includes zero and one million; both endpoints are valid. A result here is about mathematical properties of an integer, not a statement about the person who rolled it.

We keep theoretical data and observed activity separate. The full-domain table answers what can happen under the rule set. A dated leaderboard snapshot answers what was visible at capture time. Mixing those would suggest an observed rank is a permanent property of a number, or that a theoretical maximum was necessarily rolled today. Neither follows. The distinction is built into the navigation, headings, and timestamps throughout the site.

The checker calculates inside your browser and does not send the number you enter to RNGdle or to a calculation API on this site. The sandbox likewise draws and analyzes numbers locally. It may keep a short list of your recent sandbox results in this browser’s local storage so you can revisit them; clearing site storage removes that local list. No account is required for those tools.

The public day board is copied into the site at build time from a publicly readable API response. The visible table is limited to rank, number, EP, and the player’s displayed name. User IDs, heart counts, poems, and fields whose meaning is unclear are not shown. A visitor opening this static page does not cause a request to the original game. The capture time printed on the page is the time the data was obtained, not the time you loaded it.