APRS Packet Errors for DO6GZ-WX (last 24 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
20250508174306DO6GZ-WX>APRS,qAS,DO6GZ-L1:!5158.93N/00950.64E_315/00 g...t057r000p...P...h39b10200 Lux:883 WX-Alfeld-OST
20250508180400DO6GZ-WX>APRS,qAS,DO6GZ-L1:!5158.93N/00950.64E_000/00 g...t057r000p...P...h43b10201 Lux:781 WX-Alfeld-OST
20250508185618DO6GZ-WX>APRS,qAS,DO6GZ-L1:!5158.93N/00950.64E_315/00 g...t049r000p...P...h99b10206 Lux:54 WX-Alfeld-OST
20250508201957DO6GZ-WX>APRS,qAS,DO6GZ-L1:!5158.93N/00950.64E_315/00 g...t043r000p...P...h100b10214 Lux:0 WX-Alfeld-OST
20250508204052DO6GZ-WX>APRS,qAS,DO6GZ-L1:!5158.93N/00950.64E_315/00 g...t042r000p...P...h100b10215 Lux:0 WX-Alfeld-OST