About

A small tool that came out of getting the same arithmetic wrong too many times.

Why it exists

When a team is spread from Kaliningrad to Vladivostok, the failure is never the conversion itself. It is that the conversion happens in a different window, one city at a time, and the answer has already scrolled away by the time the next one is worked out. Meetings kept landing at 07:00 for somebody who was too polite to say so.

Every world clock we tried shows a column of cities with their current times. That answers "what time is it there" and never answers "when can all of us talk", which was the only question actually being asked. Drawing each city as a strip of its own day and stacking the strips against a shared timeline turns the second question into something you see rather than compute.

How it is built

Plain HTML, one stylesheet, one script. No framework, no build step, no bundler, no dependencies. The board is rendered from your browser's own clock and time zone database, which is also why it stays correct through daylight saving changes anywhere without being updated.

There is no backend. Nothing you do on the board is transmitted anywhere, because there is nowhere for it to go. The list of cities you pick sits in local storage on your own machine.

What it costs

Nothing, and there is no plan for that to change. There is no account to make, no tier to upgrade to, and no email to hand over. It is a static page on a small server, and the marginal cost of one more person opening it rounds to zero.

Cities

The eleven Russian cities on the board cover all eleven time zones of the country, one each. The rest were chosen on the same principle: a city earns a place when it represents an offset or a daylight saving rule that nothing else on the board covers. Duplicates of an existing offset make the board longer without making it more useful.