When you hear the word Bluetooth, chances are you immediately think of wireless headphones, smartphone connectivity, or that familiar blue logo on your devices. But behind this modern technology lies a surprising historical connection—one that reaches back over a thousand years to the age of the Vikings. Yes, it is indeed true: Bluetooth was named after a Viking king—Harald “Bluetooth” Gormsson, a ruler of Denmark and Norway in the 10th century. But how did an ancient monarch lend his name to a 21st-century wireless technology? Let’s dive into the fascinating story.
Who Was Harald Bluetooth?
Harald “Bluetooth” Gormsson was a 10th-century Viking king who ruled over Denmark from around 958 to 986 CE and also briefly controlled parts of Norway. He was the son of King Gorm the Old and Queen Thyra. Harald is best known for uniting much of Denmark and Norway under a single kingdom and for introducing Christianity to the Danes.
The origin of Harald’s nickname, “Bluetooth,” is still debated. One theory is that he had a dead tooth that appeared blue or dark in color. Another suggestion is that he had a fondness for blueberries, though that’s more folklore than fact. Whatever the reason, the name “Bluetooth” stuck—and it would eventually be revived a millennium later in a completely unexpected way.
The Birth of Bluetooth Technology
Fast forward to the 1990s. The tech world was evolving rapidly, with computers, phones, and other electronic devices beginning to connect and share data wirelessly. Engineers from companies like Intel, Ericsson, and Nokia were working on a short-range radio technology to allow these devices to communicate without cables.
During the development of this technology, Jim Kardach, an engineer at Intel, suggested the name “Bluetooth” as a temporary codename. Kardach, a history enthusiast, had recently read about Harald Bluetooth and was struck by the parallel: just as King Harald had unified Denmark and Norway, the new technology aimed to unify different devices and standards across platforms.The name was meant to be temporary, but it stuck. shutdown123