APRS Packet Errors for DL4ALL-95 (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
20260827235255	DL4ALL-95>APRSMC,TCPIP*,qAR,DL4ALL-12:!5016.45N/00822.60E_73 Micha/B=009/A=001362
20260828002245	DL4ALL-95>APRSMC,TCPIP*,qAR,DL4ALL-12:!5016.45N/00822.60E_73 Micha/B=008/A=001362
20260828005305	DL4ALL-95>APRSMC,TCPIP*,qAR,DL4ALL-12:!5016.45N/00822.60E_73 Micha/B=009/A=001362
20260828012320	DL4ALL-95>APRSMC,TCPIP*,qAR,DL4ALL-12:!5016.45N/00822.60E_73 Micha/B=009/A=001362
20260828015330	DL4ALL-95>APRSMC,TCPIP*,qAR,DL4ALL-12:!5016.45N/00822.60E_73 Micha/B=008/A=001362
20260828022346	DL4ALL-95>APRSMC,TCPIP*,qAR,DL4ALL-12:!5016.45N/00822.60E_73 Micha/B=007/A=001362
20260828025414	DL4ALL-95>APRSMC,TCPIP*,qAR,DL4ALL-12:!5016.45N/00822.60E_73 Micha/B=009/A=001362
20260828032424	DL4ALL-95>APRSMC,TCPIP*,qAR,DL4ALL-12:!5016.45N/00822.60E_73 Micha/B=008/A=001362
20260828035431	DL4ALL-95>APRSMC,TCPIP*,qAR,DL4ALL-12:!5016.45N/00822.60E_73 Micha/B=008/A=001362
20260828042446	DL4ALL-95>APRSMC,TCPIP*,qAR,DL4ALL-12:!5016.45N/00822.60E_73 Micha/B=008/A=001362
20260828045505	DL4ALL-95>APRSMC,TCPIP*,qAR,DL4ALL-12:!5016.45N/00822.60E_73 Micha/B=008/A=001362
20260828052516	DL4ALL-95>APRSMC,TCPIP*,qAR,DL4ALL-12:!5016.45N/00822.60E_73 Micha/B=007/A=001362