No, the Rune Meanings page does not provide rune divination or predictions. It is a historical-language and Unicode reference for the 24 characters commonly grouped as the Elder Futhark, and it deliberately stops short of any draws, forecasts, spiritual keywords, or personality claims. The catalogue lists each rune alongside its Unicode code point, transliteration, reconstructed literal gloss, aett group, and a row-level uncertainty note, so the table functions as an encoding and reconstruction reference rather than a fortune-telling instrument. Disputed entries such as Pertho (no broadly agreed literal gloss) and Algiz (disputed name, sound history, and meaning) are kept visibly uncertain instead of being smoothed into confident modern symbolism. The page answers historical research questions like which Unicode code point corresponds to ᛟ, or what literal gloss is sometimes reconstructed for Laguz, while declining to answer questions of the form what does this rune say about my relationship, money, or future.
What the Rune Meanings Page Actually Is
The tool is a literal 24-row catalogue of the Elder Futhark forms most commonly grouped as the historical runic alphabet of the early Germanic-speaking world. Each row stores the Unicode-encoded character, its standard Unicode name, its code point, a transliteration, a common reconstructed name, a literal name gloss, the aett it belongs to, its position within that aett, and an explicit uncertainty note where scholarly convention does not settle the matter. The table begins with ᚠ at U+16A0 and ends with ᛟ at U+16DF, drawing the specific Elder Futhark forms from the larger Unicode Runic block rather than mixing in later Anglo-Saxon, Younger Futhark, or variant characters. Penn State's institutional reference on Germanic Runes explains the historical Runic script families and their phonetic function, which is the same script family this catalogue indexes; the Viking Ship Museum independently states that the Elder Futhark contains 24 letters and explains the limits of reconstructed early rune names. These external sources are what allow the table to keep its facts about encoding separate from its facts about linguistic reconstruction.
Because the source data is sourced, the page can be checked the way any reference table can be checked: each character maps to exactly one code point, every row appears once, and every aett contains exactly eight entries in the conventional order. There is no commentary layer, no randomization, no changed-over-time weighting, and no decorative meaning overlay. The catalogue is read-only in the sense that nothing inside it gets rewritten between visits. The Reset button restores the full 24-entry view and selects the first entry, the same state a reader would see on first load.
What the Page Does Not Do
The page's deliberate limits are part of what makes it a reference rather than a divination tool. There are no draws, no changing layouts, no randomized selection, and no narrative overlay built on top of the table. The following list names the features the catalogue explicitly avoids, because each of them is what readers often expect from a fortune-telling experience and each of them is precisely what the tool refuses to provide:
- No "rune of the day" or randomized single-rune pick.
- No drawn three-rune spread and no positional reading prompts.
- No spiritual keyword set covering love, money, career, health, or safety.
- No personality, character, shadow, or zodiac-style diagnostic claim.
- No supernatural accuracy claim, forecast, or future-event prediction.
- No personal question intake and no interpretive paragraph written in response to a reader's situation.
Literal glosses such as cattle, gift, hail, ice, sun, horse, water, day, inheritance, or household are historical-language reference labels. They describe the words that later Germanic rune-name traditions attached to the characters, not instructions or forecasts about the reader's life. Where the convention disagrees, the table preserves the disagreement: Kauna or Kenaz may carry a qualified boil or ulcer gloss, and Eihwaz transliteration, Laguz or Laukaz naming, and several reconstructed vocalizations vary by scholarly tradition. The catalogue keeps those disagreements visible rather than replacing them with confident modern symbolism, because smoothing them over would turn a reference into an oracle.
The contrast between reference and divination can be summarized at a glance. The table below pairs what the catalogue actually delivers on the left with the oracle-style features it deliberately withholds on the right, so a reader can confirm in one place that none of the fortune-telling affordances have been quietly added under a different label.
| Reference capability (included) | Divination capability (not included) |
|---|---|
| 24-row Elder Futhark catalogue with Unicode characters, code points, and standard names | Randomized single-rune draw or "rune of the day" |
| Three aett groups of eight, displayed in the conventional sequence | Three-rune spread with positional reading prompts |
| Unicode code point, transliteration, reconstructed literal gloss, aett, and position per row | Spiritual keyword sets covering love, money, career, health, or safety |
| Row-level uncertainty notes for disputed entries such as Pertho and Algiz | Personality, character, shadow, or zodiac-style diagnostic claims |
| Browser-memory search by rune character, code point, name, transliteration, or literal gloss | Supernatural accuracy claims, forecasts, or future-event predictions |
| Reset catalogue restores all 24 entries with no fetch, storage, or analytics | Personal question intake or interpretive paragraph written in response to a reader's situation |
How to Search All 24 Elder Futhark Entries
The search interface runs entirely in the browser, and the three core operations are search, inspect, and reset. Use the following sequence to move from a known lookup term to a confirmed catalogue row:
- Type into the search field using any of the supported forms: the rune character itself (ᛟ), a common reconstructed name (such as ehwaz or tiwaz), a Unicode code point (U+16A0), a transliteration (such as f, u, or th), or a literal name gloss (such as cattle, gift, or hail).
- If you want to narrow the result to one of the three historical groups, select the corresponding aett from the aett filter. Each aett contains exactly eight entries in the displayed conventional sequence, so filtering by aett plus a partial search term is often enough to disambiguate a result.
- Choose a matching row to inspect its Unicode name, transliteration, reconstructed gloss, aett group, position inside that aett, and the row's uncertainty note where scholarly convention is divided.
- Read the uncertainty note before treating any reconstructed gloss as fact: per-row caveats flag entries such as Pertho, which has no broadly agreed literal gloss, and Algiz, whose name, sound history, and elk comparison all remain qualified.
- Use Reset catalogue to restore all 24 entries after you have finished a search session. Reset selects the first entry and clears the search field and aett filter back to their default state.
Why Reconstructed Glosses Stay Qualified
A Unicode character name is an encoding label, not proof of the word used by every ancient runewriter. The Elder Futhark inscriptions that survive did not include a complete contemporary glossary beside the alphabet, and many of the familiar names and literal meanings readers encounter in modern listings are scholarly reconstructions informed by later Germanic rune-name traditions. The catalogue therefore labels the relevant fields reconstructed or common-name literal glosses rather than presenting them as direct translations from one ancient source. Where reconstruction is uncertain, the row carries an explicit note rather than a polished summary. As one example, Perthro's lack of a broadly agreed literal gloss is recorded on its own row; as another, the Algiz row records that the common elk comparison remains qualified. The catalogue keeps those disagreements visible because hiding them would make the table easier to read and harder to trust.
How Search and Filtering Stay Private
Searching by rune character, common name, code point, transliteration, or literal gloss and filtering by aett both run in browser memory. The page makes no fetch call to a remote server for the catalogue, asks for no third-party dictionary lookup, gates no content behind an account, and writes nothing to localStorage or sessionStorage from the search controls. There is no query log, no analytics record of what was searched, and no record of which aett was selected. Reset catalogue restores the full 24-entry view and selects the first entry; it does not delete any server-side history because no server-side history exists. If the system font cannot draw a runic character, the Unicode code point and uppercase standard name remain readable, so the encoding facts survive a missing-font gap. Controls use native search and selection behavior, minimum 44-pixel targets, and visible focus treatment, and the results reflow into a single column on narrow screens, while the rune list gains a bounded vertical scroll only when the catalogue is taller than the visible window.
What the Page Is Useful For, and What It Is Not
Readers who want to confirm a code point, check a transliteration, look up a reconstructed literal gloss, or compare the rows that contain a specific rune character will find the catalogue directly useful. Readers who want a prediction about a relationship, a forecast for a financial decision, or a personalized oracle response will find that the catalogue, by design, does not give them one. The same source discipline that keeps Perthro marked as uncertain and Algiz marked as disputed is what keeps the page from drifting into confident claims about real-life outcomes. If the goal is a drawing-based self-reflection exercise with clearly labeled prompts, a separate page such as the rune reading draw tool offers a different experience under different rules. If the goal is to verify what Unicode, the historical Runic script families, and the museum record actually say about the 24 Elder Futhark characters, this catalogue is the matching tool.
How Verification Fits the Reference Role
Because the catalogue is built to be checked, the verification layer is part of the reference contract rather than a decorative add-on. Independent checks transcribe all 24 character, code-point, and Unicode-name triples and confirm that each character and code point appears only once, that the three aett groups each contain exactly eight entries, and that positions are contiguous inside every group. Literal search examples, aett filter interactions, invalid-code-point handling, reset behaviour, and uncertainty markers are tested the same way, alongside the privacy boundary (no fetch call, no third-party dictionary request, no account gate, no localStorage or sessionStorage write, no query log) and the absence of any predictive claim. Correctness, in other words, means preserving the sourced encoding facts and clearly qualified reconstruction, not validating modern divination interpretations. That is why a reader who comes to the page asking for a prediction walks away with a verified row instead of a fortune.