APRS Packet Errors for EA3HVF-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
20260208151400EA3HVF-12>APRSGW,TCPIP*,qAR,EA3HVF-12:!4122.97N/00202.57E##EA3HVF-16/B=100/A=000082
20260208154419EA3HVF-12>APRSGW,TCPIP*,qAR,EA3HVF-12:!4122.97N/00202.57E##EA3HVF-16/B=100/A=000082
20260208161434EA3HVF-12>APRSGW,TCPIP*,qAR,EA3HVF-12:!4122.97N/00202.57E##EA3HVF-16/B=100/A=000082
20260208164449EA3HVF-12>APRSGW,TCPIP*,qAR,EA3HVF-12:!4122.97N/00202.57E##EA3HVF-16/B=100/A=000082
20260208171504EA3HVF-12>APRSGW,TCPIP*,qAR,EA3HVF-12:!4122.97N/00202.57E##EA3HVF-16/B=100/A=000082
20260208174522EA3HVF-12>APRSGW,TCPIP*,qAR,EA3HVF-12:!4122.97N/00202.57E##EA3HVF-16/B=100/A=000082
20260208181537EA3HVF-12>APRSGW,TCPIP*,qAR,EA3HVF-12:!4122.97N/00202.57E##EA3HVF-16/B=100/A=000082
20260208184552EA3HVF-12>APRSGW,TCPIP*,qAR,EA3HVF-12:!4122.97N/00202.57E##EA3HVF-16/B=100/A=000082
20260208191607EA3HVF-12>APRSGW,TCPIP*,qAR,EA3HVF-12:!4122.97N/00202.57E##EA3HVF-16/B=100/A=000082
20260208194626EA3HVF-12>APRSGW,TCPIP*,qAR,EA3HVF-12:!4122.97N/00202.57E##EA3HVF-16/B=100/A=000082
20260208201641EA3HVF-12>APRSGW,TCPIP*,qAR,EA3HVF-12:!4122.97N/00202.57E##EA3HVF-16/B=100/A=000082
20260208204656EA3HVF-12>APRSGW,TCPIP*,qAR,EA3HVF-12:!4122.97N/00202.57E##EA3HVF-16/B=100/A=000082