Swatch Internet Time (.beats)

» see swatch.com as it lived, on the wayback machine

~ the obit ~

swatch announced internet time on 23 october 1998. the swiss watch company was trying to position itself as relevant to the new digital age. the pitch was that timezones were a 19th century invention that did not fit the global internet. they proposed replacing timezones with a single global time, measured in "beats."

the day was divided into 1000 beats. each beat was about 86.4 seconds. midnight at the swatch HQ meridian (biel, switzerland) was @000 beats. noon biel time was @500. the system used a leading "@" symbol so a time looked like "@350" or "@847." swatch made watches that displayed beats alongside or instead of regular hours.

i remember .beats from the dial-up era. it showed up on irc and icq status messages for a couple of years. people would say things like "ping me @500" or set their messenger nickname to include their current beat time. it was a novelty signal that you were online and tech-curious. nobody actually used it as their real time reference.

by 2002 the novelty was gone. swatch kept making beat-watches for several more years but the cultural reference faded. the last swatch products that prominently featured beat time were sold around 2009. swatch.com still has a beat-time conversion page in 2026, mostly for nostalgia.

~ the rap sheet ~

~ how it actually worked ~

the math was simple. 24 hours equals 86,400 seconds. divide by 1000 and each beat is 86.4 seconds. the day starts at @000 and reaches @999 just before midnight at the swatch meridian. you converted to beats by taking your current UTC offset, adjusting to biel mean time (UTC+1, no daylight saving), and computing the fraction of the day that had passed.

swatch published online converters and made software widgets. there was a beat clock you could put on your desktop. there were java applets that showed the current beat time. there were chrome extensions years later (the few that still got built). the calculations were trivial enough that anyone could implement them.

swatch also produced physical watches with beat displays. early models showed beats alongside regular hours. some later models showed only beats. a few collectors-edition models were entirely beat-themed. these are sold on watch enthusiast markets in 2026 as kitsch nostalgia objects, often for more than their original retail price.

~ the irc and icq era ~

.beats had a brief moment of usefulness, sort of. in 1999 to 2001, internet chat communities had members spread across many timezones. saying "let us meet at 3pm" required everyone to figure out conversions. saying "let us meet @620" was a flat number with no timezone.

this almost worked. the problem was that nobody actually adopted it as their real reference. people would convert their local time to beats, post the beat time, and other people would convert it back. it was an extra translation step pretending to be a unification step. timezones with established conversion habits were faster.

the cultural footprint was real for a few years. you would see "@500" in irc topics and discord-precursor channels. you would see beat watches on tech forums. someone would always know the current beat time off the top of their head, like the way some people always know the unix timestamp.

~ why it never took off ~

the marketing problem was obvious. swatch was a swiss company. they put the meridian at swatch HQ. that is, the entire system was branded with one company's location as the global zero point. for non-swatch users, this was hard to take seriously. it felt like a marketing gimmick because it was a marketing gimmick.

the practical problem was that timezones encode useful information. when someone says "5pm here," you know roughly where in the day they are without thinking. saying "@625" requires you to convert to figure out if that is morning, afternoon, evening. .beats removed timezone confusion at the cost of removing time-of-day intuition.

the cultural problem was that the internet had already settled on UTC for technical purposes (servers, log files, github commit times) and local time for human purposes (calendars, scheduling, daily life). there was no actual gap that .beats was filling. the proposed unification was trying to replace two working systems with a third one that did not work as well as either.

~ what it left ~

the cultural reference. .beats are a small piece of late-90s internet folklore. anyone who was online in 1999 to 2001 has at least seen the syntax. it shows up in retro tech writing as a marker of a specific moment when internet culture was feeling both globally connected and ready to overthrow established conventions.

the watches. the swatch beat watches still exist as collectibles. some hobbyist watch communities trade them. they are objectively interesting design objects from a specific moment in consumer electronics history. the value is mostly nostalgic but real.

the principle. .beats was a small example of how branding can undermine an idea. the underlying concept (a single unified internet time) had some merit. the implementation (a private company places the meridian at its own headquarters) made it impossible to take seriously. swatch was selling a global standard while also using the standard to sell more swatch watches. those goals do not align.

@}-->--

« previous  ·  random  ·  next »