APRS Packet Errors for DN9BN-99 (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
20260208150658DN9BN-99>APRSGW,TCPIP*,qAR,DN9BN-99:!5143.70N/01014.87E#Meshcom OHA#DN9BN-99/B=100/A=000732
20260208153716DN9BN-99>APRSGW,TCPIP*,qAR,DN9BN-99:!5143.70N/01014.87E#Meshcom OHA#DN9BN-99/B=100/A=000732
20260208160731DN9BN-99>APRSGW,TCPIP*,qAR,DN9BN-99:!5143.70N/01014.87E#Meshcom OHA#DN9BN-99/B=100/A=000732
20260208163746DN9BN-99>APRSGW,TCPIP*,qAR,DN9BN-99:!5143.70N/01014.87E#Meshcom OHA#DN9BN-99/B=100/A=000732
20260208170801DN9BN-99>APRSGW,TCPIP*,qAR,DN9BN-99:!5143.70N/01014.87E#Meshcom OHA#DN9BN-99/B=100/A=000732
20260208180834DN9BN-99>APRSGW,TCPIP*,qAR,DN9BN-99:!5143.70N/01014.87E#Meshcom OHA#DN9BN-99/B=100/A=000732
20260208183849DN9BN-99>APRSGW,TCPIP*,qAR,DN9BN-99:!5143.70N/01014.87E#Meshcom OHA#DN9BN-99/B=100/A=000732
20260208190904DN9BN-99>APRSGW,TCPIP*,qAR,DN9BN-99:!5143.70N/01014.87E#Meshcom OHA#DN9BN-99/B=100/A=000732
20260208193922DN9BN-99>APRSGW,TCPIP*,qAR,DN9BN-99:!5143.70N/01014.87E#Meshcom OHA#DN9BN-99/B=100/A=000732
20260208200937DN9BN-99>APRSGW,TCPIP*,qAR,DN9BN-99:!5143.70N/01014.87E#Meshcom OHA#DN9BN-99/B=100/A=000732
20260208203952DN9BN-99>APRSGW,TCPIP*,qAR,DN9BN-99:!5143.70N/01014.87E#Meshcom OHA#DN9BN-99/B=100/A=000732