Reproducible Rune Lookups Start With a Local Catalogue
The Rune Meanings catalogue holds all 24 Elder Futhark entries in a fixed, in-browser table, so repeating the same input produces the same row, the same Unicode code point, the same transliteration, and the same qualified literal gloss every time. Each rune is stored with its Unicode character (from U+16A0 to U+16DF for the Elder Futhark forms), its standard Unicode name, its transliteration, its literal name gloss, its aett group, its position within that group, and an uncertainty note where the historical record is incomplete. Searches run locally against that table — there is no fetch call, no account, no localStorage entry, no sessionStorage entry, and no query log — so the only thing that changes a result is the text you type or the filter you pick. Pressing Reset catalogue clears the filter, restores all 24 entries, and returns the table to a known starting state, which lets you run the same lookup again with a defined baseline.
That design is what makes the result repeatable. The catalogue is the source of truth, the search is a deterministic match against that catalogue, and the displayed row carries the same text labels each time. If two people type the same query into Rune Meanings, they see the same character, the same U+16A0–U+16DF code point, the same Unicode name, and the same qualified gloss. The page never invents a row on the fly, never consults a third-party dictionary, and never adjusts the row based on prior sessions.
What the Catalogue Holds for Every Entry
Each row is built from the same set of fields, and that uniform structure is what gives the table its consistency. A row carries the rune character itself, its Unicode code point, the standard Unicode name from the Unicode Runic NamesList, a transliteration such as f, u, þ, or ŋ, a reconstructed literal gloss, the aett group (first, second, or third) it belongs to, the position it holds inside that aett (1 through 8), and an uncertainty note when scholarly sources disagree.
The table below summarises how those fields line up against the kind of query you can type. Knowing which field a search matches against helps you predict which row will appear.
| Search input | Matched catalogue field | Example value | Returned row identity |
|---|---|---|---|
| Rune character | Displayed glyph column | ᚠ | Row for U+16A0, first aett, position 1 |
| Unicode code point | Code point column | U+16A0 | Same row, identified by encoding value |
| Unicode name | Standard Unicode name | FEHU | Same row, identified by encoding label |
| Transliteration | Transliteration column | f | Same row, identified by letter value |
| Literal gloss | Reconstructed gloss column | cattle or wealth | Same row, identified by gloss text |
Because every search points at the same static row, switching input types never changes which entry you end up on — it just changes which field you used to find it. The Unicode name is an encoding label rather than a historical translation, and the literal gloss is a scholarly reconstruction rather than a verified ancient definition, but the row is always the row.
How to Repeat the Same Rune Meanings Result
The catalogue is built so that the same input returns the same row. To make that repeatable in practice, work through the following steps each time you start a lookup.
- Open Rune Meanings and click Reset catalogue so the table starts with all 24 entries and the first row is selected.
- Decide which field you want to match against — character, Unicode name, code point, transliteration, or literal gloss — and type that value into the search box.
- If you only need a narrow slice of the 24, open the aett selector and pick first, second, or third before you search, so the table is already filtered when your query runs.
- Read the matching row's labels for code point, transliteration, aett, position, literal gloss, Unicode name, and uncertainty note. The row text is the repeatable output.
- To run the lookup again in a new session, press Reset catalogue and re-enter the exact same query string, or re-select the same aett filter; the row will be identical.
The reason this works is that every step above targets a fixed field. The catalogue has exactly 24 rows, each with one Unicode character, one code point, one standard Unicode name, one transliteration, and one literal gloss, so the search has no room to drift. The order of the 24 entries is also fixed: ᚠ at U+16A0 begins the table and ᛟ at U+16DF ends it, with the three aett groups of eight sitting inside that range.
Filters and the Reset Button for a Known Starting Point
Repeatability depends on a clean starting state. The Reset catalogue button is the tool that gives you one: it restores all 24 entries, clears any active search text, removes the aett filter, and selects the first row. After pressing it, the table is in the same condition it was in on first load, which means the next search begins from a defined baseline rather than whatever filter you left behind from the previous session.
The aett selector complements that baseline. Each aett — first (ᚠ to ᚹ), second (ᚺ to ᛊ), third (ᛏ to ᛟ) — contains exactly eight entries in a fixed sequence, so when you limit the table to one aett you know in advance how many rows will appear and in what order. Combining the aett filter with a search narrows the match even further; combining Reset with the aett filter gives you a precise scope that you can re-create on demand.
If you want to verify that a result really did repeat, the cleanest method is to note the row's code point and Unicode name, then close and reopen the page, press Reset, re-type the same query, and confirm that the same code point and Unicode name come back. The same code point always identifies the same row in this catalogue, because each of the 24 characters has a unique code point between U+16A0 and U+16DF.
Handling Disputed and Reconstructed Meanings
Some rows in the catalogue are not settled historically, and that can look like the catalogue is giving a different answer each time. It is not — the row is the same, but the literal gloss carries an explicit uncertainty note. Pertho, for example, has no broadly agreed literal gloss, so its row is marked as such; Algiz carries a disputed name, sound history, and meaning, with the elk comparison kept qualified; Kauna or Kenaz is shown with the qualified boil or ulcer gloss; and Eihwaz transliteration, Laguz or Laukaz naming, and several reconstructed vocalisations vary by scholarly convention. Those notes are part of the row, not a separate interpretation, so they come back identically every time you query the same entry.
The point is to distinguish reproducibility of the catalogue from certainty of the historical record. The catalogue repeats; the historical record has gaps, and the catalogue shows those gaps rather than hiding them. Pressing Reset and re-running the query will give you the same qualified gloss, the same uncertainty wording, and the same row — which is what "the same result" means inside a tool that refuses to invent modern symbolism on top of an ancient alphabet. For a fuller walkthrough of how to record what each row returns, the guide on documenting steps using Elder Futhark Rune Meanings covers how to capture the same fields each session.
Privacy, Storage, and Why Local Processing Matters
Repeatability also depends on what the tool does not do. Rune Meanings does not send your search text to a server, does not write a localStorage record, does not write a sessionStorage record, does not require an account, and does not log a query history. All searching, all filtering, and the entire catalogue itself sit in browser memory for the page session only. That is why two visits that start with a fresh Reset behave the same way: there is no hidden state carried from one visit to the next, and no remote call whose response could vary.
This design choice is consistent with how Unicode itself treats the Elder Futhark block. The Unicode Runic NamesList defines the encoded characters, code points, and standard names as stable encoding facts, and Penn State's Symbol Codes reference on Germanic Runes describes those code points as the authoritative way to identify a rune when the page font cannot render the character. Because the catalogue stores those facts rather than re-deriving them on every load, the same code point always names the same row, even if the rune glyph is missing from a font. Wikipedia's Elder Futhark entry covers the 24-rune structure and the limits of the reconstructed rune names that the catalogue marks as such. With local processing and a fixed 24-row table, the result of any given lookup is a function of your input alone.
Related reading: Rune Combinations and Contradictions in a Three-Rune Spread.