APRS Packet Errors for DM1CR-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
20260209092308	DM1CR-12>APRSGW,TCPIP*,qAR,DM1CR-12:!4803.84N/01137.70E>#DM1CR/B=100/A=001847
20260209095322	DM1CR-12>APRSGW,TCPIP*,qAR,DM1CR-12:!4803.84N/01137.70E>#DM1CR/B=100/A=001847
20260209102337	DM1CR-12>APRSGW,TCPIP*,qAR,DM1CR-12:!4803.84N/01137.70E>#DM1CR/B=100/A=001847
20260209105353	DM1CR-12>APRSGW,TCPIP*,qAR,DM1CR-12:!4803.84N/01137.70E>#DM1CR/B=100/A=001847
20260209112408	DM1CR-12>APRSGW,TCPIP*,qAR,DM1CR-12:!4803.84N/01137.70E>#DM1CR/B=100/A=001847
20260209115423	DM1CR-12>APRSGW,TCPIP*,qAR,DM1CR-12:!4803.84N/01137.70E>#DM1CR/B=100/A=001847
20260209122438	DM1CR-12>APRSGW,TCPIP*,qAR,DM1CR-12:!4803.84N/01137.70E>#DM1CR/B=099/A=001847
20260209125451	DM1CR-12>APRSGW,TCPIP*,qAR,DM1CR-12:!4803.84N/01137.70E>#DM1CR/B=100/A=001847
20260209132506	DM1CR-12>APRSGW,TCPIP*,qAR,DM1CR-12:!4803.84N/01137.70E>#DM1CR/B=100/A=001847
20260209135521	DM1CR-12>APRSGW,TCPIP*,qAR,DM1CR-12:!4803.84N/01137.70E>#DM1CR/B=100/A=001847
20260209142536	DM1CR-12>APRSGW,TCPIP*,qAR,DM1CR-12:!4803.84N/01137.70E>#DM1CR/B=100/A=001847
20260209145550	DM1CR-12>APRSGW,TCPIP*,qAR,DM1CR-12:!4803.84N/01137.70E>#DM1CR/B=100/A=001847