APRS Packet Errors for DL2TIM-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
20260209120529	DL2TIM-12>APRSGW,TCPIP*,qAR,DL2TIM-12:!4902.16N/00822.31E-#DL2Tim-7/B=100/A=000535
20260209123547	DL2TIM-12>APRSGW,TCPIP*,qAR,DL2TIM-12:!4902.16N/00822.31E-#DL2Tim-7/B=100/A=000535
20260209130602	DL2TIM-12>APRSGW,TCPIP*,qAR,DL2TIM-12:!4902.16N/00822.31E-#DL2Tim-7/B=100/A=000535
20260209133617	DL2TIM-12>APRSGW,TCPIP*,qAR,DL2TIM-12:!4902.16N/00822.31E-#DL2Tim-7/B=100/A=000535
20260209140632	DL2TIM-12>APRSGW,TCPIP*,qAR,DL2TIM-12:!4902.16N/00822.31E-#DL2Tim-7/B=100/A=000535
20260209143648	DL2TIM-12>APRSGW,TCPIP*,qAR,DL2TIM-12:!4902.16N/00822.31E-#DL2Tim-7/B=100/A=000535
20260209150703	DL2TIM-12>APRSGW,TCPIP*,qAR,DL2TIM-12:!4902.16N/00822.31E-#DL2Tim-7/B=100/A=000535
20260209153718	DL2TIM-12>APRSGW,TCPIP*,qAR,DL2TIM-12:!4902.16N/00822.31E-#DL2Tim-7/B=100/A=000535
20260209160733	DL2TIM-12>APRSGW,TCPIP*,qAR,DL2TIM-12:!4902.16N/00822.31E-#DL2Tim-7/B=100/A=000535
20260209163749	DL2TIM-12>APRSGW,TCPIP*,qAR,DL2TIM-12:!4902.16N/00822.31E-#DL2Tim-7/B=100/A=000535
20260209170804	DL2TIM-12>APRSGW,TCPIP*,qAR,DL2TIM-12:!4902.16N/00822.31E-#DL2Tim-7/B=100/A=000535
20260209173819	DL2TIM-12>APRSGW,TCPIP*,qAR,DL2TIM-12:!4902.16N/00822.31E-#DL2Tim-7/B=100/A=000535