APRS Packet Errors for DL2MT-11 (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
20260209131704	DL2MT-11>APRSGW,TCPIP*,qAR,DL2MT-11:!5336.64N/00716.98E-/B=100/A=000144
20260209133347	DL2MT-11>APRSGW,TCPIP*,qAR,DL2MT-11:!5336.64N/00716.98E-/B=100/A=000144
20260209140402	DL2MT-11>APRSGW,TCPIP*,qAR,DL2MT-11:!5336.64N/00716.98E-/B=100/A=000144
20260209143417	DL2MT-11>APRSGW,TCPIP*,qAR,DL2MT-11:!5336.64N/00716.98E-/B=100/A=000144
20260209150432	DL2MT-11>APRSGW,TCPIP*,qAR,DL2MT-11:!5336.64N/00716.98E-/B=100/A=000144
20260209153447	DL2MT-11>APRSGW,TCPIP*,qAR,DL2MT-11:!5336.64N/00716.98E-/B=100/A=000144
20260209160502	DL2MT-11>APRSGW,TCPIP*,qAR,DL2MT-11:!5336.64N/00716.98E-/B=100/A=000144
20260209163517	DL2MT-11>APRSGW,TCPIP*,qAR,DL2MT-11:!5336.64N/00716.98E-/B=100/A=000144
20260209170535	DL2MT-11>APRSGW,TCPIP*,qAR,DL2MT-11:!5336.64N/00716.98E-/B=100/A=000144
20260209173550	DL2MT-11>APRSGW,TCPIP*,qAR,DL2MT-11:!5336.64N/00716.98E-/B=100/A=000144
20260209180605	DL2MT-11>APRSGW,TCPIP*,qAR,DL2MT-11:!5336.64N/00716.98E-/B=100/A=000144
20260209183620	DL2MT-11>APRSGW,TCPIP*,qAR,DL2MT-11:!5336.64N/00716.98E-/B=100/A=000144
20260209190639	DL2MT-11>APRSGW,TCPIP*,qAR,DL2MT-11:!5336.64N/00716.98E-/B=100/A=000144