Amin Call Clock
A free, offline-capable world clock for planning calls from Pakistan. No account, backend, tracking, API key, or paid service is required.
Install on iPhone
- Open the published HTTPS address in Safari.
- Wait until the clock page says “Ready offline”.
- Tap Share, then Add to Home Screen. Enable “Open as Web App” if shown, then tap Add.
- Open Amin Clock from your Home Screen once while online before using it offline.
On Windows, use your browser’s Install app option in Edge or Chrome, or the in-app Install button when available. Installation is optional.
City coverage
34,154 GeoNames records across 244 countries and territories are bundled. This is the cities15000 extract: cities with a population above 15,000 or capitals, according to GeoNames. It includes some smaller administrative capitals and urban districts. It is not a directory of every town, suburb, or business.
Search matches city names, ASCII spellings, state/province names, country names and country codes. Records retain their GeoNames ID, region and supplied IANA timezone. No coordinate-based or country-based timezone is guessed. Select the exact city and region in the results. If a town is missing, choose a known city in the same timezone only after independently confirming that it shares your prospect’s timezone.
City data was downloaded on 7 October 2026 and adapted by Amin Call Clock: fields were selected, administrative and country labels joined, and records ordered by population. Data is provided as-is and may contain inaccuracies.
Attribution: GeoNames, licensed under Creative Commons Attribution 4.0. Original data documentation.
Timezone rules
All calculations use bundled IANA 2026e rules through Moment 2.30.1 and Moment Timezone 0.6.5, rather than the browser’s own timezone database. Both libraries are MIT licensed: Moment licence and Moment Timezone licence. IANA timezone data is public domain.
The converter and planning controls support 2000–2100. Future times are predictions under the bundled rules; governments can change those rules. Rebuild with a newer verified database and republish when rules change.
- 2026b: British Columbia’s America/Vancouver stays at UTC−07 after its March 2026 spring change.
- 2026c: Alberta’s America/Edmonton stays at UTC−06; Morocco also changes to permanent UTC in September.
- 2026d: America/Inuvik stays at UTC−06, covering the Northwest Territories change.
- 2026e: Manitoba’s America/Winnipeg stays at UTC−05, with the legal change on 31 October 2026. IANA currently applies the same rule to associated northwestern Ontario areas and notes that this may change.
Toronto, Ottawa, Montreal and Halifax still follow their own seasonal rules. Phoenix does not switch to daylight saving. Adelaide and Darwin retain their half-hour offsets; Adelaide changes seasonally and Darwin does not.
How schedules work
Each city starts with Monday–Friday, 8 a.m.–5 p.m. opening hours and a preferred 9–11 a.m. window. Edit these on any card. Hours must start and finish on the same local date; overnight business hours are not supported. Windows include the start and exclude the end.
“Weekend” means any non-working day in that city’s configured week. Public holidays are not included. The next window includes a window already in progress (“Open now”), or the next future working day. The planning date applies to the city’s local calendar date; leaving it blank uses each city’s own today.
The suggested 8–11 a.m. and 2–4 p.m. windows are experiments, not guaranteed best times. They must fit your configured opening hours.
When clocks repeat a time, the converter asks you to select the earlier or later occurrence. Schedules flag repeated times by default, with an explicit earlier/later setting available per city. Nonexistent local times are rejected, never silently shifted. A problematic upcoming window is flagged for review instead of being quietly skipped.
Offline use & privacy
Live clocks always use the actual device timestamp and refresh immediately when you return to the app. Accurate device time is essential. The app cannot detect a wrongly set device clock.
All essential assets, city records and timezone rules are saved by the service worker after the first successful online load. No third-party runtime request is required. Favourites, display choices and schedules are stored in localStorage on this browser and origin. They do not sync between devices. Clearing site data removes them; browsers can evict offline caches. Private browsing can limit persistence.
App updates activate after all old app tabs/windows are closed. Reopen online to obtain new data. This avoids mixing an old screen with new timezone rules mid-session.