Elder Futhark rune meanings displayed in the Rune Meanings catalogue are not certain ancient definitions; they are scholarly reconstructions drawn from later Germanic rune-name traditions, with each row's uncertainty marked explicitly. The catalogue treats Unicode names and code points as encoding facts while flagging familiar labels such as 'cattle', 'gift', 'hail', and 'sun' as reconstructed or common-name literal glosses rather than direct translations from one ancient source. Elder Futhark inscriptions did not preserve a complete contemporary glossary beside the alphabet, so any literal meaning you read is informed by later evidence and convention, not extracted verbatim from a single runestone. That distinction is the whole reason the tool labels its fields 'reconstructed' or 'Unicode name' rather than presenting them as confident translations. Each of the 24 rows carries an explicit uncertainty note so you can see, at a glance, where scholars agree, where they disagree, and where no broadly agreed literal gloss survives at all.
What the Catalogue Actually Contains
The Rune Meanings catalogue is built from a literal 24-row table that pairs each Elder Futhark character with two distinct kinds of information: encoding facts and reconstructed language labels. Encoding facts come from the Unicode Runic NamesList and include the character itself (such as ᚠ), its code point (U+16A0 for the first rune), and its standard Unicode name. These are stable, verifiable, and identical across every conformant implementation of the Runic block, and the table selects the specific Elder Futhark forms from the larger Runic Unicode block rather than mixing in later runic variants.
Reconstructed language labels are something different. They are the familiar names, Fehu, Uruz, Thurisaz, Ansuz, Raidho, Kenaz, Gebo, and Wunjo for the first aett, with similar pairs for the second and third, plus literal name glosses like 'cattle', 'gift', 'hail', 'ice', 'sun', 'horse', 'water', 'day', 'inheritance', and 'household'. These names and glosses are not lifted from a single ancient dictionary; they are scholarly reconstructions informed by later Germanic rune-name traditions. The catalogue keeps that distinction visible by labeling the relevant fields as 'reconstructed' or 'common-name literal gloss' rather than presenting them as direct ancient translations. A Unicode character name is an encoding label, not proof of the word used by every ancient runewriter, and the table treats it that way throughout every row.
| Field | Source | Certainty |
|---|---|---|
| Rune character (ᚠ, ᛟ, …) | Unicode Runic block | Encoding fact |
| Unicode code point (U+16A0, U+16DF, …) | Unicode NamesList | Encoding fact |
| Standard Unicode name | Unicode NamesList | Encoding label, not a translation |
| Common reconstructed name (Fehu, Ansuz, …) | Later Germanic rune-name tradition | Scholarly reconstruction |
| Transliteration (f, u, þ, a, r, k/c, g, w …) | Convention varies by source | Convention-dependent |
| Literal name gloss ('cattle', 'gift', 'sun' …) | Comparative Germanic linguistics | Reconstruction, often qualified |
| Aett group and position (1–8 within group) | Conventional grouping | Conventional, not always uniform in antiquity |
| Uncertainty note | Row-specific scholarly assessment | Explicit per entry |
Searching and Filtering the 24-Rune Catalogue
- Open the Rune Meanings catalogue and choose how you want to search: by rune character, by Unicode code point, by the standard Unicode name, by a common reconstructed name, by transliteration, or by the literal name gloss. Type any of those into the search field; the catalogue normalizes its 24 rows locally so each lookup runs in browser memory without a network call, and there is no fetch call, third-party dictionary request, account gate, localStorage record, sessionStorage record, or query log from the widget.
- If you want to narrow the visible set to one third of the alphabet, select the first, second, or third aett from the aett filter. Each aett groups eight runes in the conventional sequence, so selecting one aett returns eight rows even when the search field is empty, and the filter combines with text search when both are active.
- Pick a matching row to inspect its Unicode name, code point, transliteration, reconstructed or common-name literal gloss, aett position, and the row-specific uncertainty note. Every result carries text labels for each of those fields, so meaning never depends on decoration alone, and the note is the place to look when you need to know whether a particular entry is widely agreed, disputed, or has no broadly accepted literal gloss.
- Click Reset catalogue to restore the full 24-entry list and clear any aett filter. Reset also selects the first row so you can start a fresh inspection from ᚠ at U+16A0, the beginning of the conventional Elder Futhark sequence, with ᛟ at U+16DF marking the end of the encoded range.
How Uncertainty Is Marked Per Rune
Because the catalogue's job is to be explicit about what is and is not settled, every row carries an uncertainty note that names the specific problem for that entry. A few examples show how the notes work in practice. Perthro (ᛈ, U+16C8) is marked as having no broadly agreed literal gloss, and the catalogue deliberately does not invent one. Algiz (ᛇ, U+16C7) is flagged for a disputed name, sound history, and meaning, and the common elk comparison is presented as qualified rather than confirmed. Kauna or Kenaz (ᚲ, U+16B2) is shown with the qualified 'boil' or 'ulcer' gloss used by the selected independent table rather than as a confident 'torch' translation. Eihwaz (ᛃ, U+16C3) has transliteration conventions that vary by scholarly source. Laguz or Laukaz (ᛚ, U+16DA) has competing forms for the name itself, and several reconstructed vocalizations across the catalogue vary by convention. The interface keeps those disagreements visible instead of replacing them with a single confident modern symbolism, so a reader never has to guess whether a familiar label is settled or contested.
If you only have time to read one field on a busy day, read the uncertainty note. The code point and the Unicode name are encoding facts; the literal gloss and the reconstructed name are reconstructions. The note tells you how much weight each reconstruction will bear, and it is the only place where the catalogue makes a per-row statement about whether a particular ancient meaning is certain at all. That row-level honesty is the main reason the tool avoids the kind of confident single-word summary you sometimes see on rune posters, and it is also why no row in the catalogue can be lifted out of context and treated as a stand-alone definition.
What the Tool Does Not Claim
It is worth being direct about what Rune Meanings does not do, because the search query behind this article often comes from a reader who wants to know whether the catalogue crosses from reference into prediction. It does not. The catalogue does not assign modern spiritual keywords, draw a rune, calculate a reading, diagnose personality, forecast an outcome, or claim supernatural accuracy. Literal name glosses such as 'cattle', 'gift', 'hail', 'ice', 'sun', 'horse', 'water', 'day', 'inheritance', and 'household' are historical-language reference labels, not instructions about romance, money, health, career, safety, or future events. The interface is built around that boundary rather than around it.
That boundary matters because it is the difference between a source-bounded reference and a divination tool. If you are looking for a reading, this is not the right place. If you are looking for a careful, reconstructed, explicitly qualified historical-language reference for the 24 Elder Futhark characters, it is. Readers who want the same reference-style approach to a different historical system can compare it with the I Ching hexagram meanings reference guide, which takes a similar source-bounded, no-prediction approach to the 64 King Wen hexagrams. Both catalogues stay on the reference side of the line and label their reconstructions as reconstructions, and both treat the underlying source authority (Unicode encoding in one case, classical text traditions in the other) as something to describe accurately rather than to dramatize.
Where the Underlying Facts Come From
The catalogue rests on three independent bodies of evidence, and it keeps them visibly separate rather than blending them into a single claim. The first is the Unicode Runic NamesList, which provides the authoritative encoded characters, code points, and standard names. Every code-point field in the table traces back to that source, and tests independently transcribe all 24 character, code-point, and Unicode-name triples to verify that each character and code point is unique. The second is Penn State's Symbol Codes reference on Germanic Runes, an institutional reference that explains the historical Runic script families, their phonetic function, Unicode encoding, and the practical point that missing fonts will show boxes instead of glyphs, in which case the Unicode code point and uppercase standard name remain readable on the page.
Together these sources provide the encoding facts and the historical framing. The Penn State reference also explains the phonetic role each rune played, which is why the catalogue's transliteration column can present convention-dependent values without overstating any one of them as the original pronunciation. The Viking Ship Museum independently states that Elder Futhark contains 24 letters and explains the limits of reconstructed early rune names, which is the broader scholarly context the catalogue leans on when it labels literal glosses as reconstructions. None of these sources, on their own, justify treating a familiar rune name as a certain ancient definition, and the catalogue is built around that shared limitation rather than around any one of them.
Accessibility and Layout Details Worth Noting
Several practical design choices in the catalogue exist so the reference stays usable even when conditions are not ideal. Controls use native search and selection behavior, minimum 44-pixel targets, and visible focus treatment, which matters when a reader is switching between keyboard and pointer. Results reflow into a single column on narrow screens, while the rune list gains a bounded vertical scroll only when needed rather than forcing a tall fixed panel. Every result carries text labels for code point, transliteration, aett, position, literal gloss, Unicode name, and uncertainty, so a reader using a screen reader or a text-only view receives the same information as a reader viewing glyphs. Verification checks 24 external Unicode goldens, three aett groups of exactly eight, contiguous positions within each group, literal search examples, filter interactions, reset behavior, invalid code-point handling, uncertainty markers, privacy boundaries, and the absence of predictive claims, which is how the catalogue keeps its reference claims honest without slipping into validation of modern divination interpretations.