Published core pages
42
Based on locker-detail and data-standard pages
Service snapshot
A quick summary of the data coverage currently maintained by BogwanBogwan and the transparency we provide around our sources.
Live-data areas
4
Areas supported by operator or data integrations
Mixed-support areas
9
Areas that combine live integrations and survey coverage
Survey-based areas
29
Pages based on field checks and public information
Latest review month
Apr 2026
Most recent review timing across location data
Data sources
Our base dataset combines public transport information, operator notices, facility guidance, field-check records, and user reports. Rather than relying on a single source, we compare multiple signals and prioritize guidance that is genuinely useful in real use cases.
For pages marked as real-time, we prioritize operator data delivered through APIs. For areas without live integration, we explicitly show the survey timing and explanatory labels so visitors can clearly distinguish between live and non-live guidance.
- We start with official notices and operator information.
- We recheck items that require repeated confirmation.
- Reports are applied after internal review.
What 'real-time' and 'survey-based' mean
A 'real-time' label means the page is supported by operator-connected status or availability signals, and the interface is designed to take users back to the live map immediately. Even then, short-lived discrepancies may still occur due to on-site connectivity or timing gaps.
A 'survey-based' label means the page focuses on recently checked location details, access guidance, common operating patterns, and fallback tips. These pages are best used for planning before arrival, while final availability still needs to be confirmed on-site.
Update standards
Information is reviewed regularly, and changes that directly affect user decisions, such as operator notices and location or pricing changes, are updated as quickly as possible. When something cannot be confirmed immediately, we present it conservatively based on the current verification level.
Our priorities favor high-demand hubs, areas with live integrations, and pages that recently received reports. Another important principle is that we do not try to make older pages look fresher than they really are.
- Update timestamps are managed in internal records.
- Unclear information is displayed conservatively.
- Correction requests are reviewed with priority.
How correction requests are handled
Correction requests move faster when they include the page URL, the exact field that needs to change, and a supporting link or photo. We do not publish reports as-is; we cross-check them with operator guidance or additional evidence before deciding whether to update the page.
- Review is faster when the request includes the page URL, screenshots, and an official reference link.
- If a report conflicts with operator guidance, we keep the page conservative until additional verification is complete.
- For urgent on-site issues, we direct users to the facility's official support channel first.
Current limitations
BogwanBogwan is not a reservation or on-site operations service; it is a planning and guidance service designed to help before arrival. For pages without live integration, we do not guarantee vacancy, exact pricing, or operating hours.
Locker information web service built on public and open data•We share our source standards, update rules, and correction process.