Overview
When a Location has an opening-hours Calendar and time zone assigned, Mobaro counts Downtime only during the hours the Location is open, so overnight and after-hours closures don't inflate the totals. This article explains the rule and works through how it plays out, including across multiple days. For how to attach the Calendar and time zone in the first place, see Add opening hours to a Location.
Why this matters: Downtime percentage is only meaningful if it's measured against the time a ride was actually meant to run. Opening hours are what make that possible — without them, a fault logged at 2 AM on a closed ride counts just as much as one during peak hours, and your uptime looks far worse than reality.
Note: The opening-hours Calendar is only for Downtime calculation. It does not schedule Checklists and is not the same thing as a Schedule or a Checklist scheduling Calendar — even though all Calendars share one object type. See the comparison in Add opening hours to a Location.
The core rule
Once an opening-hours Calendar and time zone are assigned to a Location:
Downtime inside the opening-hours window counts toward totals.
Downtime outside those hours is ignored.
If a Downtime begins before opening or runs past closing, only the in-hours portion counts.
Mobaro applies this automatically everywhere Downtime appears — the Downtime overview, Dashboards, reports, and exports — interpreting every Location's hours in its assigned time zone.
Heads-up: Downtime is recalculated when it is closed, not while it's open. Before closing, a Downtime can look longer than it really is because it still includes out-of-hours time. Once closed, Mobaro recalculates to the accurate in-hours duration.
Example: a single day
A Location's opening hours are 10 AM–6 PM. A ride goes down at 4 PM and is resolved at 8 PM.
Mobaro counts 2 hours of Downtime (4 PM–6 PM). The 6 PM–8 PM period is excluded because it falls outside opening hours — so an evening fault on an already-closed ride doesn't distort the day's figures.
Example: spanning multiple days
When a Downtime spans several days, Mobaro checks each day's operating window and counts only the in-hours portion of each. With operating hours of 10 AM–6 PM daily and a ride down from Friday 4 PM until Sunday 10 AM:
Friday: 2 hours (4 PM–6 PM).
Saturday: 8 hours (10 AM–6 PM, the full operating day).
Sunday: 0 hours (resolved at 10 AM, before the operating day effectively begins).
Best practice: For the formulas behind these figures — Nominal Operational Hours and Downtime Percentage — and how to adjust a suggested duration when closing, see How Mobaro calculates Downtime registrations.
Frequently asked questions
Q: Can I use the same Calendar for a Schedule and for opening hours?
A: It's technically possible since both use the same Calendar object type, but it rarely makes sense — a Checklist's availability window and a ride's open-to-close hours are usually different. Create a dedicated opening-hours Calendar instead.
Q: What happens if I forget to set the time zone?
A: Mobaro can't interpret the hours correctly, so Downtime totals will be off. Always set the time zone when assigning the Calendar.
Q: Why does a Downtime look longer before it's closed?
A: The duration is finalized on close. While open, the timer shows all elapsed time, including any out-of-hours portion.
Q: What happens if a Downtime overlaps opening or closing time?
A: Only the portion inside operating hours counts. Time before opening or after closing is trimmed once the Downtime is closed.
Q: What if no opening-hours Calendar is assigned?
A: Downtime is measured across the full 24-hour day, so out-of-hours time is not trimmed.