meetergo data
Meeting data, published with its method
Charts drawn from 1,609,703 booked meetings and 1,171,388 attendee time zones in meetergo's production database. Aggregated, non-identifiable and free to cite.
Every figure on this page comes from a query run on August 20, 2026. Where a number needs a filter to be true, and most of them do, the filter is in the subhead rather than in a footnote.
- Meetings analysed
- 1,609,703
- Attendee time zones
- 1,171,388
- German domestic meetings
- 983,062
- European markets charted
- 5
Across every booking channel, all time.
180 days. All but one of them carries a real local time zone.
365 days, attendee and host on the same clock, cancellations excluded.
Nothing below 3,000 domestic meetings gets a line.
Reports
One recurring index, the meeting clock, plus occasional one-offs. Each report states its sample size, its window, and the confound it removed before the finding was believed.
- Working patternsEurope
Europe's lunch break, measured in a million meetings
Five European markets, five midday dips, and France's arrives a full hour after everybody else's.
August 20, 2026n = 1,060,456
- Working patternsGermany
Germany does not have a workday. It has two.
983,062 domestic German meetings, one deep notch at noon, and a second peak that never quite catches the first.
August 20, 2026n = 983,062
- SalesBooking behaviour
Only 14% of meetings are booked for today or tomorrow
841,480 completed meetings, sorted by the gap between booking and start. The speed-to-lead orthodoxy describes a seventh of them.
August 20, 2026n = 841,480
How we collect this data
meetergo is scheduling software used across Europe. The reports here are a by-product of running it: aggregate patterns in when meetings get booked and when they start.
Production data, not a survey
Every figure is a query against the live appointment, attendee and host tables. Nobody was asked what time they prefer to meet: these are the meetings that actually happened.
The method travels with the number
Sample size, window and filter sit in the subhead of every chart, and the SQL sits at the bottom of every report. Run it against your own book if you have one.
Re-run each quarter
Working hours are seasonal: summer hours, the December collapse, the January surge. The meeting clock is re-queried rather than republished unchanged.
Aggregated and non-identifiable
meetergo sells GDPR compliance, so no cut is fine enough to trace back to one customer's booking volume. Every market shown clears a minimum sample of 3,000 meetings.
What we don't publish
Four chart ideas were tested against this data. One survived unchanged. These are the four checks that killed the others, and they now run before any design work starts.
- 01
Coverage before design
A field filled in on 43% of rows cannot carry a claim, however good the chart looks. Referrer coverage killed an entire concept after the design was finished. The fill rate gets checked first now.
- 02
What the field measures, not what it is called
A no-show flag that a host ticks by hand measures how diligent hosts are, not how many people showed up. We publish attendance when it is measured, not when it is asserted.
- 03
Confound removed before the finding is believed
Without the domestic filter, an attendee's local meeting hour is set by the host's calendar rather than by local habit. It changed the answer here, which is exactly why it is stated on the chart.
- 04
Margin checked against sample size
An afternoon peak leading by three bookings on a sample of 13,186 is not a peak. One finding in this set was cut in review for exactly that.
100.0%
Attendee time zone coverage
1,171,388 attendees over 180 days. The strongest field in the dataset, and the one the meeting clock is built on.
43.3%
Referrer coverage
268,005 bookings since attribution shipped. The weakest field in the dataset, and the reason nothing here is built on referrers.
Replace five tools with one. Add only the apps you need.
Start with scheduling. Turn on forms, video, CRM and AI notes only when they fit your workflow.
No credit card required. Cancel anytime.