APRS Packet Errors for SP9VNR-5 (last 6 hours)

This table contains packets in which findU has detected an error. This is an automated system, no manual checking of these packets has been done. Most common cause of this is mistakes in entering the latitude/longitude into hard-coded digis, or positions of 0/0. If packets of yours appear here, and you have looked at it carefully and cannot find the error, look again. I've been watching these error messages in my log, and believe my parser is reasonably correct. Go get the APRS spec to be sure. If you have done that, and are CERTAIN the packet is a legal APRS packet, then it is possible that there is an error in my my parser. Only email me if you are absolutely, positively certain...ask yourself, would I bet $100!

time (UTC)	Packet
20260208163301	SP9VNR-5>APBM1D,SR9VJK,DMR*,qAR,SR9VJK:@163259h4925.26N/02057.60E/129/010Jurek
20260208163411	SP9VNR-5>APBM1D,SR9VJK,DMR*,qAR,SR9VJK:@163409h4925.25N/02057.99E/107/022Jurek
20260208163513	SP9VNR-5>APBM1D,SR9VJK,DMR*,qAR,SR9VJK:@163511h4925.18N/02058.26E/113/001Jurek
20260208180121	SP9VNR-5>APBM1D,SR9VJK,DMR*,qAR,SR9VJK:@180119h4925.18N/02058.24E/000/000Jurek
20260208180223	SP9VNR-5>APBM1D,SR9VJK,DMR*,qAR,SR9VJK:@180221h4925.28N/02057.88E/277/019Jurek
20260208180325	SP9VNR-5>APBM1D,SR9VJK,DMR*,qAR,SR9VJK:@180323h4925.32N/02057.55E/327/007Jurek
20260208180427	SP9VNR-5>APBM1D,SR9VJK,DMR*,qAR,SR9VJK:@180425h4925.55N/02057.33E/327/014Jurek
20260208180533	SP9VNR-5>APBM1D,SR9VJK,DMR*,qAR,SR9VJK:@180531h4925.83N/02057.17E/338/007Jurek