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
20260208132658DO7KB-12>APRSGW,TCPIP*,qAR,DO7KB-12:!5221.31N/01432.00E#MeshCom FFO/B=074/A=000305
20260208135713DO7KB-12>APRSGW,TCPIP*,qAR,DO7KB-12:!5221.31N/01432.00E#MeshCom FFO/B=047/A=000305
20260208142729DO7KB-12>APRSGW,TCPIP*,qAR,DO7KB-12:!5221.31N/01432.00E#MeshCom FFO/B=062/A=000305
20260208145742DO7KB-12>APRSGW,TCPIP*,qAR,DO7KB-12:!5221.31N/01432.00E#MeshCom FFO/B=040/A=000305
20260208152757DO7KB-12>APRSGW,TCPIP*,qAR,DO7KB-12:!5221.31N/01432.00E#MeshCom FFO/B=038/A=000305
20260208155812DO7KB-12>APRSGW,TCPIP*,qAR,DO7KB-12:!5221.31N/01432.00E#MeshCom FFO/B=062/A=000305
20260208162832DO7KB-12>APRSGW,TCPIP*,qAR,DO7KB-12:!5221.31N/01432.00E#MeshCom FFO/B=056/A=000305
20260208165847DO7KB-12>APRSGW,TCPIP*,qAR,DO7KB-12:!5221.31N/01432.00E#MeshCom FFO/B=081/A=000305
20260208172902DO7KB-12>APRSGW,TCPIP*,qAR,DO7KB-12:!5221.31N/01432.00E#MeshCom FFO/B=050/A=000305
20260208175917DO7KB-12>APRSGW,TCPIP*,qAR,DO7KB-12:!5221.31N/01432.00E#MeshCom FFO/B=030/A=000305
20260208182931DO7KB-12>APRSGW,TCPIP*,qAR,DO7KB-12:!5221.31N/01432.00E#MeshCom FFO/B=051/A=000305