APRS Packet Errors for DO7KB-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
20260209161001DO7KB-12>APRSGW,TCPIP*,qAR,DO7KB-12:!5221.31N/01432.00E#MeshCom FFO/B=038/A=000305
20260209164016DO7KB-12>APRSGW,TCPIP*,qAR,DO7KB-12:!5221.31N/01432.00E#MeshCom FFO/B=042/A=000305
20260209171031DO7KB-12>APRSGW,TCPIP*,qAR,DO7KB-12:!5221.31N/01432.00E#MeshCom FFO/B=052/A=000305
20260209174046DO7KB-12>APRSGW,TCPIP*,qAR,DO7KB-12:!5221.31N/01432.00E#MeshCom FFO/B=070/A=000305
20260209181101DO7KB-12>APRSGW,TCPIP*,qAR,DO7KB-12:!5221.31N/01432.00E#MeshCom FFO/B=040/A=000305
20260209184116DO7KB-12>APRSGW,TCPIP*,qAR,DO7KB-12:!5221.31N/01432.00E#MeshCom FFO/B=067/A=000305
20260209191132DO7KB-12>APRSGW,TCPIP*,qAR,DO7KB-12:!5221.31N/01432.00E#MeshCom FFO/B=028/A=000305
20260209194146DO7KB-12>APRSGW,TCPIP*,qAR,DO7KB-12:!5221.31N/01432.00E#MeshCom FFO/B=056/A=000305
20260209201201DO7KB-12>APRSGW,TCPIP*,qAR,DO7KB-12:!5221.31N/01432.00E#MeshCom FFO/B=028/A=000305
20260209204212DO7KB-12>APRSGW,TCPIP*,qAR,DO7KB-12:!5221.31N/01432.00E#MeshCom FFO/B=080/A=000305
20260209211228DO7KB-12>APRSGW,TCPIP*,qAR,DO7KB-12:!5221.31N/01432.00E#MeshCom FFO/B=039/A=000305
20260209214242DO7KB-12>APRSGW,TCPIP*,qAR,DO7KB-12:!5221.31N/01432.00E#MeshCom FFO/B=074/A=000305