APRS Packet Errors for DG3IAM-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
20260209094654DG3IAM-12>APRSGW,TCPIP*,qAR,DG3IAM-12:!4852.18N/00811.89E#Meshcom Gateway#Rastatt / Rheinau/B=100/A=000410
20260209101709DG3IAM-12>APRSGW,TCPIP*,qAR,DG3IAM-12:!4852.18N/00811.89E#Meshcom Gateway#Rastatt / Rheinau/A=000410
20260209104724DG3IAM-12>APRSGW,TCPIP*,qAR,DG3IAM-12:!4852.18N/00811.89E#Meshcom Gateway#Rastatt / Rheinau/B=071/A=000410
20260209111739DG3IAM-12>APRSGW,TCPIP*,qAR,DG3IAM-12:!4852.18N/00811.89E#Meshcom Gateway#Rastatt / Rheinau/A=000410
20260209114754DG3IAM-12>APRSGW,TCPIP*,qAR,DG3IAM-12:!4852.18N/00811.89E#Meshcom Gateway#Rastatt / Rheinau/B=100/A=000410
20260209121809DG3IAM-12>APRSGW,TCPIP*,qAR,DG3IAM-12:!4852.18N/00811.89E#Meshcom Gateway#Rastatt / Rheinau/B=100/A=000410
20260209124824DG3IAM-12>APRSGW,TCPIP*,qAR,DG3IAM-12:!4852.18N/00811.89E#Meshcom Gateway#Rastatt / Rheinau/B=100/A=000410
20260209134854DG3IAM-12>APRSGW,TCPIP*,qAR,DG3IAM-12:!4852.18N/00811.89E#Meshcom Gateway#Rastatt / Rheinau/B=100/A=000410
20260209141909DG3IAM-12>APRSGW,TCPIP*,qAR,DG3IAM-12:!4852.18N/00811.89E#Meshcom Gateway#Rastatt / Rheinau/A=000410
20260209144924DG3IAM-12>APRSGW,TCPIP*,qAR,DG3IAM-12:!4852.18N/00811.89E#Meshcom Gateway#Rastatt / Rheinau/A=000410