APRS Packet Errors for DL1MPL-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
20260208130335	DL1MPL-12>APRSGW,TCPIP*,qAR,DL1MPL-12:!5000.52N/00846.82E#/B=100/A=000653
20260208133350	DL1MPL-12>APRSGW,TCPIP*,qAR,DL1MPL-12:!5000.52N/00846.82E#/B=100/A=000653
20260208140407	DL1MPL-12>APRSGW,TCPIP*,qAR,DL1MPL-12:!5000.52N/00846.82E#/B=100/A=000653
20260208143422	DL1MPL-12>APRSGW,TCPIP*,qAR,DL1MPL-12:!5000.52N/00846.82E#/B=100/A=000653
20260208150434	DL1MPL-12>APRSGW,TCPIP*,qAR,DL1MPL-12:!5000.52N/00846.82E#/B=100/A=000653
20260208153449	DL1MPL-12>APRSGW,TCPIP*,qAR,DL1MPL-12:!5000.52N/00846.82E#/B=100/A=000653
20260208160504	DL1MPL-12>APRSGW,TCPIP*,qAR,DL1MPL-12:!5000.52N/00846.82E#/B=100/A=000653
20260208163520	DL1MPL-12>APRSGW,TCPIP*,qAR,DL1MPL-12:!5000.52N/00846.82E#/B=100/A=000653
20260208170535	DL1MPL-12>APRSGW,TCPIP*,qAR,DL1MPL-12:!5000.52N/00846.82E#/B=100/A=000653
20260208173550	DL1MPL-12>APRSGW,TCPIP*,qAR,DL1MPL-12:!5000.52N/00846.82E#/B=100/A=000653
20260208180605	DL1MPL-12>APRSGW,TCPIP*,qAR,DL1MPL-12:!5000.52N/00846.82E#/B=100/A=000653
20260208183620	DL1MPL-12>APRSGW,TCPIP*,qAR,DL1MPL-12:!5000.52N/00846.82E#/B=100/A=000653