2025-05-30, 16:31
That’s a great observation, and you’re not the only one who’s noticed this kind of behavior.
What you’re describing sounds like a data filtering or post-processing issue. Sometimes, lightning networks (like Blitzortung or similar) show preliminary real-time data that later gets removed if the strike couldn’t be reliably triangulated by enough stations—especially in areas with limited coverage like parts of Scotland. So even if it looked accurate in the moment (and matched what you heard), it might not meet the backend confidence threshold for inclusion in the archive or -24h views.
It can definitely be frustrating when you know it happened but the historical record doesn’t show it!
Hope that helps clear it up a bit!
What you’re describing sounds like a data filtering or post-processing issue. Sometimes, lightning networks (like Blitzortung or similar) show preliminary real-time data that later gets removed if the strike couldn’t be reliably triangulated by enough stations—especially in areas with limited coverage like parts of Scotland. So even if it looked accurate in the moment (and matched what you heard), it might not meet the backend confidence threshold for inclusion in the archive or -24h views.
It can definitely be frustrating when you know it happened but the historical record doesn’t show it!
Hope that helps clear it up a bit!