APRS Packet Errors for DL4ALL-12 (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
20260914143436DL4ALL-12>APRSMC,TCPIP*,qAR,DL4ALL-10:!5016.45N/00822.60E_73 Micha/B=008/A=001362
20260914150445DL4ALL-12>APRSMC,TCPIP*,qAR,DL4ALL-10:!5016.45N/00822.60E_73 Micha/B=008/A=001362
20260914160515DL4ALL-12>APRSMC,TCPIP*,qAR,DL4ALL-10:!5016.45N/00822.60E_73 Micha/B=008/A=001362
20260914163530DL4ALL-12>APRSMC,TCPIP*,qAR,DL4ALL-10:!5016.45N/00822.60E_73 Micha/B=008/A=001362
20260914170545DL4ALL-12>APRSMC,TCPIP*,qAR,DL4ALL-10:!5016.45N/00822.60E_73 Micha/B=007/A=001362
20260914173600DL4ALL-12>APRSMC,TCPIP*,qAR,DL4ALL-10:!5016.45N/00822.60E_73 Micha/B=007/A=001362
20260914180615DL4ALL-12>APRSMC,TCPIP*,qAR,DL4ALL-10:!5016.45N/00822.60E_73 Micha/B=008/A=001362
20260914183638DL4ALL-12>APRSMC,TCPIP*,qAR,DL4ALL-10:!5016.45N/00822.60E_73 Micha/B=007/A=001362
20260914190645DL4ALL-12>APRSMC,TCPIP*,qAR,DL4ALL-10:!5016.45N/00822.60E_73 Micha/B=007/A=001362
20260914193700DL4ALL-12>APRSMC,TCPIP*,qAR,DL4ALL-10:!5016.45N/00822.60E_73 Micha/B=008/A=001362