APRS Packet Errors for DO6GZ (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
20260731102506DO6GZ>APRS,qAO,DO6GZ-2:!5158.93N/00950.64E_315/00 g...t084r000p...P...h90b10158 Lux:2526 WX-Alfeld-OST
20260731120941DO6GZ>APRS,qAO,DO6GZ-2:!5158.93N/00950.64E_315/00 g...t087r000p...P...h79b10149 Lux:3197 WX-Alfeld-OST
20260731123036DO6GZ>APRS,qAO,DO6GZ-2:!5158.93N/00950.64E_000/00 g...t085r000p...P...h100b10147 Lux:2976 WX-Alfeld-OST
20260731132254DO6GZ>APRS,qAO,DO6GZ-2:!5158.93N/00950.64E_000/00 g...t086r000p...P...h72b10149 Lux:3723 WX-Alfeld-OST
20260731133322DO6GZ>APRS,qAO,DO6GZ-2:!5158.93N/00950.64E_135/00 g...t086r000p...P...h70b10150 Lux:3916 WX-Alfeld-OST
20260731143607DO6GZ>APRS,qAO,DO6GZ-2:!5158.93N/00950.64E_315/00 g...t086r000p...P...h70b10149 Lux:3357 WX-Alfeld-OST
20260731162042DO6GZ>APRS,qAO,DO6GZ-2:!5158.93N/00950.64E_135/00 g...t084r000p...P...h62b10147 Lux:2150 WX-Alfeld-OST