About viking town names
Old Norse endings do the geographic work in results like "Gislavotn", "Raumsdalr", and "Gilsbakki", marking lakes, dales, and riverbanks the way real Scandinavian and Icelandic places still do. They belong on longship-era maps, saga retellings, and the northern coast of any fantasy continent. Short forms like "Skagi" read as old fishing villages, while longer compounds suggest younger inland steads.
How viking town names are built
A single Markov chain grows each settlement name letter-by-letter from a large 1154-entry attested bank of Norse and Scandinavian place names, output as one word. The chain reproduces Old Norse toponymic endings, so -ing, -en, and -sted tails recur. Bank outputs include Balling, Borken, and Austested.
Balling
Markov-synthesised, with an -ing tail
Borken
Markov-synthesised, with an -en tail
Austested
Markov-synthesised, with a -sted tail
Naming notes
The phonetic tell is the Scandinavian place-suffix set the chain inherits, -ing, -en, -ken, and the settlement-marking -sted (Austested), which echo real Danish and Norwegian town names without copying them. The 1154-entry bank is among the largest single pools in the batch, so variety is high and outputs read as one fused place word. Use these for Norse villages, trading ports, and raider home-towns; they are coinages tuned to the recorded sound, not attested settlements.
Questions about viking town names
- How are Viking town names generated?
- One Markov chain runs over a 1154-entry bank of Norse place names, producing each next letter, so each output is one synthesised place word.
- Why do they end in -ing, -en, or -sted?
- Scandinavian toponyms carry those settlement suffixes, and the chain learns them from the corpus, yielding forms like Balling and Austested.
- What are these for?
- They suit Norse villages, trading ports, and raider home-towns on a map rather than real attested Scandinavian cities.