APRS Packet Errors for DO2HN-11 (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
20260208133226DO2HN-11>APRX29,TCPIP*,qAS,DO2HN:!5049.55NI01443.66E&APRS AFSK 70cm RX-iGate on RPi
20260208140840DO2HN-11>APRX29,TCPIP*,qAS,DO2HN:!5049.55NI01443.66E&APRS AFSK 70cm RX-iGate on RPi
20260208144401DO2HN-11>APRX29,TCPIP*,qAS,DO2HN:!5049.55NI01443.66E&APRS AFSK 70cm RX-iGate on RPi
20260208152131DO2HN-11>APRX29,TCPIP*,qAS,DO2HN:!5049.55NI01443.66E&APRS AFSK 70cm RX-iGate on RPi
20260208155926DO2HN-11>APRX29,TCPIP*,qAS,DO2HN:!5049.55NI01443.66E&APRS AFSK 70cm RX-iGate on RPi
20260208163645DO2HN-11>APRX29,TCPIP*,qAS,DO2HN:!5049.55NI01443.66E&APRS AFSK 70cm RX-iGate on RPi
20260208171136DO2HN-11>APRX29,TCPIP*,qAS,DO2HN:!5049.55NI01443.66E&APRS AFSK 70cm RX-iGate on RPi
20260208174536DO2HN-11>APRX29,TCPIP*,qAS,DO2HN:!5049.55NI01443.66E&APRS AFSK 70cm RX-iGate on RPi
20260208182331DO2HN-11>APRX29,TCPIP*,qAS,DO2HN:!5049.55NI01443.66E&APRS AFSK 70cm RX-iGate on RPi
20260208190009DO2HN-11>APRX29,TCPIP*,qAS,DO2HN:!5049.55NI01443.66E&APRS AFSK 70cm RX-iGate on RPi