How accurate is this clock?
It is exactly as accurate as your device's clock. The tool reads the current instant from your system every second and formats it into each zone using the browser's time-zone database. It does not query an NTP or time server, so if your machine is a minute fast, every city on the board is a minute fast.
Where do the daylight-saving rules come from?
From your browser and operating system, which ship the IANA time-zone database. That is why the offset shown for a city changes with the season without anything being downloaded, and it is also why a very old, unpatched device can show a wrong offset for a country that has recently changed its DST rules.
My city is not in the list. What can I do?
Pick any city on the same IANA zone; the time will be identical. The list is a curated 44 zones covering the world's major offsets, not the full IANA set. There is no free-text entry, so if you need an obscure zone, choose the nearest listed city that shares its rules.
Do my chosen cities stay on the board next time?
No. The board lives in page state and resets to the defaults on reload, plus your own detected zone. There is no local storage and no account, so nothing about where you are or who you work with is retained.
Why does one of the rows show an offset like UTC+05:30?
Because some zones are genuinely offset by a fraction of an hour. India is UTC+05:30 year-round, Nepal is UTC+05:45, and parts of Australia use half-hour offsets. The tool computes the offset in minutes and renders it as hours and minutes, which is the only correct way to show it.