APRS Packet Errors for IK2CNF-20 (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
20260208163511IK2CNF-20>APRSGW,TCPIP*,qAR,IK2CNF-20:!4541.70N/00938.78E-/B=100/A=000935
20260208170534IK2CNF-20>APRSGW,TCPIP*,qAR,IK2CNF-20:!4541.70N/00938.78E-/B=096/A=000935
20260208173556IK2CNF-20>APRSGW,TCPIP*,qAR,IK2CNF-20:!4541.70N/00938.78E-/B=100/A=000935
20260208180618IK2CNF-20>APRSGW,TCPIP*,qAR,IK2CNF-20:!4541.70N/00938.78E-/B=100/A=000935
20260208183641IK2CNF-20>APRSGW,TCPIP*,qAR,IK2CNF-20:!4541.70N/00938.78E-/B=100/A=000935
20260208190703IK2CNF-20>APRSGW,TCPIP*,qAR,IK2CNF-20:!4541.70N/00938.78E-/B=100/A=000935
20260208193725IK2CNF-20>APRSGW,TCPIP*,qAR,IK2CNF-20:!4541.70N/00938.78E-/B=096/A=000935
20260208200747IK2CNF-20>APRSGW,TCPIP*,qAR,IK2CNF-20:!4541.70N/00938.78E-/B=094/A=000935
20260208203810IK2CNF-20>APRSGW,TCPIP*,qAR,IK2CNF-20:!4541.70N/00938.78E-/B=100/A=000935
20260208210832IK2CNF-20>APRSGW,TCPIP*,qAR,IK2CNF-20:!4541.70N/00938.78E-/B=100/A=000935
20260208213854IK2CNF-20>APRSGW,TCPIP*,qAR,IK2CNF-20:!4541.70N/00938.78E-/B=100/A=000935
20260208220917IK2CNF-20>APRSGW,TCPIP*,qAR,IK2CNF-20:!4541.70N/00938.78E-/B=100/A=000935