Google Maps Timezone & Local Time Lookup avatar

Google Maps Timezone & Local Time Lookup

Pricing

from $3.00 / 1,000 results

Go to Apify Store
Google Maps Timezone & Local Time Lookup

Google Maps Timezone & Local Time Lookup

Resolve the IANA timezone, current local time, UTC offset, and daylight-saving information for any coordinate. Accepts single or batch lat/lng inputs.

Pricing

from $3.00 / 1,000 results

Rating

0.0

(0)

Developer

Crawler Bros

Crawler Bros

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Share

Resolve the IANA timezone, current local time, UTC offset, and daylight-saving status for any latitude/longitude on Earth. Designed to complement other Google Maps actors when you need to normalise business hours, schedule notifications across regions, or enrich geocoded data with timezone context.

What this actor does

  • Resolves one or many public coordinates to an IANA timezone and current local time.
  • Preserves the exact coordinate input and the public timeapi.io source URL.
  • Reports current UTC offset and daylight-saving information when the source exposes it.
  • Omits unavailable fields instead of inserting guessed timezone or country values.

Output per location

For each input coordinate, the actor returns one record with:

  • inputLocation — the original {lat, lng} you provided
  • timezone — IANA zone name (e.g. America/New_York, Asia/Tokyo, Australia/Sydney)
  • timezoneAbbreviation — short code when DST is in effect (e.g. EDT, BST)
  • utcOffset — current offset formatted as +HH:MM / -HH:MM
  • utcOffsetSeconds — current offset in seconds (positive east of UTC)
  • currentLocalTime — wall-clock time at the coordinate, ISO 8601 (second resolution)
  • currentUtcTime — equivalent UTC time, ISO 8601 with Z
  • dayOfWeek — provider's ISO weekday enum when present
  • unixTimestamp — provider's Unix timestamp in seconds when present
  • isDaylightSavingTime — true when DST is currently active
  • daylightSavings — an object containing inEffect and observed, and, when available, nextTransition, dstName, standardUtcOffset, standardUtcOffsetSeconds, dstOffsetSeconds, dstUtcOffsetSeconds, startsAt, and endsAt; optional values are omitted when the provider does not return valid data
  • sourceUrl — the exact public timeapi.io coordinate endpoint used for this row
  • scrapedAt — UTC timestamp of when the lookup was performed
  • recordType — actor record discriminator (timezone)

Empty/null fields are omitted automatically.

Input

FieldTypeRequiredDescription
locationobject {lat, lng}ConditionalA single coordinate. Provide this OR locations.
locationsarray of {lat, lng}ConditionalMultiple coordinates resolved in one run.
proxyConfigurationproxyOptionalDirect HTTP is tried first; a hardcoded Apify US RESIDENTIAL retry is available for restricted outbound environments.

At least one of location or locations must be provided. Latitude must be in [-90, 90] and longitude in [-180, 180]. Synonyms latitude / longitude / lon are also accepted.

Examples

Example: global coordinate batch

{
"locations": [
{"lat": 40.7128, "lng": -74.0060},
{"lat": 51.5074, "lng": -0.1278},
{"lat": 35.6762, "lng": 139.6503},
{"lat": -33.8688, "lng": 151.2093}
]
}

Example: one coordinate with a fractional offset

{
"location": {"lat": 27.7172, "lng": 85.3240}
}

Example: mixed city coordinates

{
"locations": [
{"lat": 40.7128, "lng": -74.0060},
{"lat": 35.6762, "lng": 139.6503}
]
}

Time values are generated at request time and are intentionally not shown as a fixed output snapshot. dayOfWeek, unixTimestamp, and DST transition datapoints are included only when the provider returns valid values.

Use cases

  • Normalise business hours — combine with a places scraper to convert "9 AM - 5 PM" into UTC ranges.
  • Schedule outreach — only send notifications during local business hours per recipient.
  • Compliance & reporting — stamp events with the correct local time and DST flag.
  • Travel apps — show local time at a destination given lat/lng.

FAQ

Does this require a Google Maps API key? No. The actor calls TimeAPI's public documented v1 coordinate endpoint without cookies, login, or an API key. Provider availability and any rate limits remain provider-controlled; no unlimited quota or SLA is assumed.

Do I need a proxy? No login or cookies are involved: this actor queries the public timezone service over HTTP. It tries direct HTTP first and then a bounded hardcoded Apify US RESIDENTIAL retry if the direct request fails; explicit {"useApifyProxy": false} keeps direct-only behavior.

How accurate is the timezone for borders / disputed regions? TimeAPI documents IANA timezone identifiers. The actor preserves the returned zone and offset rather than inferring a timezone from longitude; boundary and disputed-area assignments remain provider data. Fractional offsets are retained in seconds (for example +05:45).

What happens with invalid coordinates? Out-of-range or non-numeric inputs are rejected with a clear error before any network calls are made.

Can I resolve thousands of coordinates? The input accepts batches and processes them sequentially with a short delay. Throughput depends on TimeAPI availability, provider rate limits, and the actor's run-time limit; split very large batches and validate a modest sample first.

Limits & notes

  • Country / countryCode fields are not included in the output because timeapi.io does not return them. Pair this actor with the google-maps-geocoding actor when you need country context for the same coordinate.
  • timezoneAbbreviation is populated only when the legacy response includes a DST name and DST is active; the documented v1 response does not currently expose an abbreviation, so this field may be omitted.
  • The actor prefers the documented /api/v1/timezone/coordinate JSON response and falls back to the legacy route only if the provider retires that route (HTTP 404/405/410).

You are responsible for using this data lawfully and in line with Google's terms.

🗺️ Complete Google Maps Scraper Suite

This actor is part of a comprehensive Google Maps data extraction toolkit by crawlerbros. All actors run cookielessly on the free Apify plan with bounded direct, retry, and residential recovery paths, and return clean, structured data.

ActorWhat it does
🏢 Google Maps Business ScraperExtract business data — name, address, phone, website, rating, reviews, hours, amenities
⭐ Google Maps Reviews ScraperScrape reviews with reviewer Local Guide level, photos, mentioned items, owner replies
📸 Google Maps Photos ScraperExtract all photos from any place — max-resolution URLs, contributor info, categories
🕐 Google Maps Business Hours ScraperFull 7-day hours, timezone, current local time, next open/close, holiday hours
📊 Google Maps Popular Times ScraperBusy hours histogram for all 7 days + current busyness + typical visit time
📧 Google Maps Email ExtractorFind business emails + social media links by crawling websites
🗺️ Google Maps Area ScannerGeographic grid scanning — bypass the 120-place limit with bounding box / circle / polygon
💼 Google Maps Leads ScraperB2B lead generation with email + phone enrichment, US states + global countries
🤖 Google Maps MCP ServerUnified MCP server combining search + reviews for AI assistants
🧭 Google Maps Directions ScraperA→B routing — distance, duration, traffic, route alternatives for driving/walking/transit
📍 Google Maps Geocoding ScraperBidirectional geocoding — address ↔ coordinates, with address components
🔗 Google Maps Similar Places Scraper"People also search for" / related place discovery — competitor & alternative finder
🍽️ Google Maps Menu ScraperRestaurant menu items, prices, descriptions, photos
📌 Google Maps Nearby ScraperFind places near a coordinate point — lightweight POI search by category
📋 Google Maps Place List ScraperExtract Google's curated "Top X in Y" lists — best hotels/restaurants/things to do