RNGdle share decoder: turn shared text into a number.

Which text formats are accepted

A label followed by a separator and the value works in any capitalisation: "Number: 123321", "Number=123321" and "roll #482913" are all read correctly. A message that is nothing but digits, such as "123321", is also accepted. The separator matters: "Roll 482913" with only a space is not recognised, because the decoder does not want to guess which word in a sentence is the number.

One number, or nothing

If the text contains several candidates, or no recognisable label, the decoder refuses instead of guessing. Two labelled numbers in one message are rejected rather than picking the first, because ambiguity is the most common source of a wrong analysis. The error message tells you what the expected shape looks like, and trimming the text to a single labelled value resolves it.

What it does not decode

This is not a decoder for RNGdle's private share payload. It reads plain text, not an encoded format, and it cannot recover a number from an image, from a screenshot, or from a link that does not contain the digits in its text. If a shared message hides the number behind a picture, the only reliable route is to ask for the value in text.

What happens after decoding

The extracted value is analysed with the same engine as every other tool, and the result card lists its patterns and their exact frequency in the supported range. From there you can compare it with a one-digit variation in the sandbox, or share it back as a prefilled link so the person you are talking to sees the same breakdown.

What is stored

Nothing from the pasted text is saved by the application. The text is used to extract the candidate number, the analysis is computed on the server without storing submitted values, and any history kept afterwards lives in this browser on this device only.

How to share a number from this site

If you analysed a value here and want someone else to see the same breakdown, the share action builds a link that opens the sandbox with that number prefilled. The recipient sees the identical result card because the analysis runs again on the same engine, and nothing about your session travels with the link beyond the number itself.

Troubleshooting a rejected message

Three shapes fail by design: text with no label and no separator, messages containing two labelled values, and values outside 0 to 1,000,000. Rewrite the message as a single labelled line, for example "Number: 123321", and it will resolve. If a chat app rewrites the text and strips punctuation, paste the value on its own instead — a message that is only digits is always accepted.

Which formats work best?

A label, a separator and the value, such as "Number: 123321" or "Roll: 482913". Separators are a colon, an equals sign or a hash. Plain digits on their own also work when the whole message is the number.

Why was my text rejected?

Either no labelled number was found, or more than one candidate was present. Text such as "Roll 482913" without a separator also fails by design. Trimming the message to one labelled value fixes all three cases.

Does the decoder store the text I paste?

No. The text is used to extract the number for analysis and is not saved by the application, and submitted numbers are not written to the project database.

Can it read a number out of an image?

No. The decoder reads text only. A screenshot of a roll has to be transcribed into text before it can be analysed here.

What if the message contains two numbers?

The decoder refuses, because it cannot tell which one was meant. Split the message and analyse each value separately rather than letting the tool pick one for you.

Does it decode RNGdle share links?

No. It extracts a number from plain text. A private share payload is a different format that this page does not read, and it does not claim to reverse-engineer one.

Where does the number go after decoding?

Into the standard analysis used across the toolkit. You can then open it in the sandbox, compare it with a variation, or share it as a link that prefills the same value for whoever opens it.

Why insist on a label instead of finding any digits?

Because text contains dates, scores, prices and timestamps. Searching for any digits would frequently analyse the wrong value, and a confidently wrong result is worse than an explicit refusal.

Can I paste a whole chat message?

Yes, as long as it contains exactly one labelled number. Extra surrounding words are ignored, but a second labelled value or an extra standalone number in the same message makes the text ambiguous and it will be rejected.

What if the number has a currency symbol or a comma?

Strip the punctuation first. The decoder expects plain digits after the label, so "Number: 1,234" fails while "Number: 1234" resolves to 1234.

Does it work with numbers longer than the supported range?

No. Values above 1,000,000 are refused, matching the limit used by every other tool. The message comes back as a rejection rather than a truncated analysis of the first seven digits.

Can I share the decoded result back?

Yes. After analysis the share action creates a link to the sandbox with that number prefilled, so the other person sees the same breakdown without retyping anything.

Does it matter which order the label and number appear?

Yes. The label must come first, as in "Number: 123321". A message that leads with the digits and then explains them is treated as unlabelled text and will be rejected unless the whole message is a bare number.

Can it read a number written in words?

No. The decoder matches digits, so "one hundred and twenty-three" is not recognised. Convert the words to figures first if the message you received spells the value out.

Does the label have to be in English?

Yes, the two recognised labels are "number" and "roll". Other languages are not matched, so a translated label will be rejected even when the digits behind it are valid.