The Elder Futhark Rune Meanings catalogue is a 24-character historical-language reference, not a divination or prediction tool. It groups the encoded Elder Futhark forms into three conventional aett groups of eight, beginning with ᚠ at U+16A0 and ending with ᛟ at U+16DF, drawn from the larger Unicode Runic block. Each row records the character, its Unicode code point, its standard Unicode name, a transliteration, a reconstructed common-name gloss, the aett and position, and an explicit uncertainty note. You can search by typing any of those fields into the search box, optionally narrow the table to a single aett, inspect a matching row, and then use Reset to restore all 24 entries. Searches and filters run only in your browser: nothing is stored locally, sent to a server, or logged. Because literal glosses such as "cattle," "gift," "hail," "ice," "sun," "horse," "water," "day," "inheritance," and "household" are historical-language labels — many of them scholarly reconstructions informed by later Germanic rune-name traditions rather than a single ancient glossary — the catalogue keeps those reconstructions visible alongside the Unicode encoding facts rather than turning them into modern spiritual keywords or predictive claims.
What the Elder Futhark Rune Meanings Catalogue Actually Contains
The first thing to know before opening the page is exactly what kind of reference you are looking at. The catalogue lists 24 characters commonly grouped as the Elder Futhark, the oldest fully attested form of the runic script families used by Germanic-speaking communities in the early centuries CE. It selects the specific Elder Futhark forms from the larger Unicode Runic block rather than every later or variant character that block also encodes. Penn State's institutional reference explains the historical Runic script families, their phonetic function, Unicode encoding, and the possibility that missing fonts show boxes, and that same source frames the catalogue's choice to use Unicode as the encoding authority for character identity.
The 24 entries are arranged in the conventional sequence, broken into three aett groups of eight: the first aett (positions 1–8), the second aett (positions 9–16), and the third aett (positions 17–24). The table spans the code points U+16A0 through U+16DF. That specific range is the authoritative source for the encoded characters, code points, and standard Unicode names — Unicode itself is what defines the encoding labels you see in the Unicode name column, and the catalogue verifies that each character and code point is unique across the 24 rows.
What the catalogue deliberately does not do is equally important to grasp before you begin. It 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. If you specifically want to draw runes for self-reflection, that is a different task with different rules and a different tool.
Your First Search in the Catalogue
The interface is built around a literal search field and an aett selector. A simple, three-step workflow covers most first-time use.
- Open the Elder Futhark Rune Meanings catalogue in your browser. Leave the aett selector on its default state if you want all 24 entries visible at once.
- Type into the search box using any one of five normalized fields: the rune character itself (such as ᚠ), the Unicode code point (such as U+16A0), the standard Unicode name (such as RUNIC LETTER F), the transliteration (such as f), or a literal name gloss (such as cattle). Search runs locally against normalized catalogue fields, so capitalization and whitespace do not matter.
- Click the entry that matches your query to inspect its Unicode name, transliteration, reconstructed gloss, aett position, and the explicit uncertainty note attached to that row.
If nothing matches, the search is purely literal — it does not fuzzy-match similar Unicode names or invent related glosses — and your query never leaves the browser. You can correct the entry, switch search field, or use Reset catalogue at any time.
Filtering to a Single Aett When You Need a Subset
When you only want one aett — for example, because you are cross-referencing a specific group from a textbook — use the aett selector alongside the search field. The selector narrows the displayed table to positions 1–8, 9–16, or 17–24, with positions contiguous within each group of eight. Search and filter combine: a query while a specific aett is selected returns only matching entries from that aett, instead of every rune in the full table with that term anywhere in its reconstructed fields.
This is also the cleanest way to read the table without scrolling past rows you don't currently care about. Because the rune list gains a bounded vertical scroll only when needed, narrowing to one aett keeps the layout compact on narrow screens and lets you step through eight rows at a time.
A quick comparison of what each search field matches:
| Search by | Example input | What you find |
|---|---|---|
| Rune character | ᚠ | The exact encoded form in the catalogue |
| Unicode code point | U+16A0 | The same character identified by its encoding label |
| Unicode name | RUNIC LETTER F | The standard Unicode character name for that code point |
| Transliteration | f | The phonetic letter value used in scholarly convention |
| Literal name gloss | cattle | Runes whose reconstructed common-name gloss contains the word |
If you want a fuller walk-through of the same search options in a slightly different framing, see the guide on confirming whether Elder Futhark really contains 24 runes and how to search them.
Reading a Row: What Each Field Tells You
Once an entry is selected, every result carries text labels for code point, transliteration, aett, position, literal gloss, Unicode name, and uncertainty, so meaning never depends on decoration alone. Three distinctions matter most when you read the row.
First, the Unicode name is an encoding label, not proof of the word used by every ancient runewriter. Elder Futhark inscriptions did not preserve a complete contemporary glossary beside the alphabet. Many familiar names and literal meanings are scholarly reconstructions informed by later Germanic rune-name traditions, and the catalogue therefore labels its gloss field reconstructed or common-name rather than presenting it as a direct translation from one ancient source.
Second, uncertainty is recorded per row. Pertho has no broadly agreed literal gloss. Algiz has disputed name, sound history, and meaning, and the common elk comparison remains qualified. Kauna or Kenaz is shown with the qualified boil or ulcer gloss used by the selected independent table. Eihwaz transliteration, Laguz or Laukaz naming, and several reconstructed vocalizations vary by scholarly convention. The catalogue keeps those disagreements visible instead of replacing them with confident modern symbolism.
Third, if your system font cannot draw a Runic character, the Unicode code point and uppercase standard name remain readable. 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 — so a row never disappears just because the decoration fails to render.
Resetting the Catalogue and Restoring All 24 Entries
Reset catalogue is the cleanest way to clear any active search or filter and step back from a single row. Pressing it restores the full 24-entry catalogue, brings the layout back to its default aett, and re-selects the first entry. Because all search and filter state is held in browser memory only, Reset does not need to communicate with any external system to do that — it simply re-renders the local catalogue.
This is also the right control to reach for when you have finished inspecting a row and want to compare it against the rest of the table. You are not "deleting" anything: the underlying catalogue is identical on every load, and Reset is just the button that puts the page back to that starting state.
Privacy and What Never Leaves Your Browser
The catalogue is built around a strict privacy boundary that matters for first-time users. Search and aett filtering run entirely in browser memory. There is no fetch call, no third-party dictionary request, no account gate, no localStorage record, no sessionStorage record, and no query log from the widget. Your typed query, the entry you click, and the aett you choose are never persisted in a way that survives the page reload.
That privacy boundary also shapes what verification looks like. Correctness here means preserving the sourced Unicode encoding facts and clearly qualified reconstruction — it does not mean validating modern divination interpretations, because the catalogue does not produce them. If you specifically need to understand the boundary between historical-language reference and modern prediction, the guide on whether the rune meanings page provides divination or predictions walks through the same distinction in more depth.
You can use the catalogue the same way you would use any other historical reference: open the page, type into the search field, narrow by aett, click a row, read the row's uncertainty note, and reset when you are done. Each step is local, reversible, and bound to the table on the page rather than to any account, file, or server. 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 — so the catalogue's reliability comes from what it preserves and what it refuses to invent, not from any promise that it can read your future.