Property timezones
Every property on BGApartman has one timezone, detected from where it sits on the map. Check-in and checkout times, stay dates and cancellation deadlines all follow that local clock. This page explains where the timezone comes from, what it affects, and what happens when clocks change.
On this page
The short version
- Each property has one timezone, taken from its location on the map.
- Check-in, checkout, stay dates and deadlines use the property's local time, not your device's.
- The timezone is recorded with your booking and does not change when the listing is edited.
- Daylight-saving changes come from the named timezone; one day always counts as 24 hours.
Why one shared timezone
A stay happens at the property, so its schedule is written on the property's clock. When a listing says check-in is from 14:00, that means 14:00 where the property is, the time that matters for keys, staff and the house itself.
A single timezone also keeps deadlines unambiguous. A cancellation deadline is one exact moment in time, wherever in the world the guest is reading it.
Where the timezone comes from
Hosts do not choose a timezone. BGApartman detects it from the property's location.
-
Place the map pin
The host sets the address and drops the pin on the exact property.
-
Detect the zone
The coordinates resolve to a named zone, such as Europe/Belgrade.
-
Times follow it
The listing, bookings and deadlines all use that local time.
The result is a named IANA timezone, not a fixed number like UTC+2. A named zone carries the region's daylight-saving rules, so the correct offset applies on every date of the year.
If a pin lands where more than one timezone is possible, the host is asked to move it to the exact property instead of the system guessing. If detection fails, the field offers a retry before the listing can be published.
Hosts see the detected timezone as a read-only value in the Location and House rules sections of their listing.
What uses the property timezone
-
Check-in and checkout times
Arrival and departure hours are local to the property.
-
Stay dates
Friday to Sunday means the property's Friday and Sunday, not yours.
-
Cancellation deadlines
Each deadline shows the property's zone and the offset that applies on that date.
-
The review window
The 90-day review window after checkout ends in the property's local time.
Locked in when you book
When you send a booking request, the property's timezone and the exact check-in and checkout moments are recorded with the booking.
If the host later edits the listing, even its address or map pin, your booked times, cancellation deadlines and review window stay exactly as they were. A listing edit only affects new requests.
How time is counted
Time before check-in is counted in elapsed hours, so one day always means 24 hours, even across a daylight-saving change. Three days before check-in is exactly 72 hours before the recorded check-in moment.
Each deadline shows the offset that applies on its own date, so the hour is never ambiguous.
The same moment, two clocks
14:00, property local time in Belgrade
16:00 in Dubai during summer time, 17:00 in winter
The property's clock does not move; only the offset on your own clock changes.
When clocks change
Twice a year, local clocks move forward or back by an hour. If a local time does not exist because the hour was skipped, or happens twice because the hour was repeated, BGApartman rejects that time instead of quietly shifting it.
Hosts see a clear message and can choose a different time; guests never receive a check-in moment that was silently moved. The named timezone supplies the rule, so nobody needs to know which countries observe daylight saving.
-
Spring forward
A skipped hour does not exist, so we ask for a different time.
-
Autumn back
A repeated hour is ambiguous, so we ask for a different time.
Related help
Still have questions? Contact our support team