APRS Packet Errors for DK4HPA-1 (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
20260208151912DK4HPA-1>APRSMC,TCPIP*,qAR,DO2LRF-11:!5326.61N/01023.42E-Geesthacht#Peter E30/B=100/A=000213
20260208154923DK4HPA-1>APRSMC,TCPIP*,qAR,DK0NDR-12:!5326.61N/01023.42E-Geesthacht#Peter E30/B=100/A=000213
20260208161941DK4HPA-1>APRSMC,TCPIP*,qAR,DO2LRF-11:!5326.61N/01023.42E-Geesthacht#Peter E30/B=100/A=000213
20260208165009DK4HPA-1>APRSMC,TCPIP*,qAR,DO2LRF-11:!5326.61N/01023.42E-Geesthacht#Peter E30/B=100/A=000213
20260208173405DK4HPA-1>APRSGW,TCPIP*,qAR,DK4HPA-1:!5326.61N/01023.42E-Geesthacht#Peter E30/B=100/A=000213
20260208180420DK4HPA-1>APRSGW,TCPIP*,qAR,DK4HPA-1:!5326.61N/01023.42E-Geesthacht#Peter E30/B=100/A=000213
20260208183435DK4HPA-1>APRSGW,TCPIP*,qAR,DK4HPA-1:!5326.61N/01023.42E-Geesthacht#Peter E30/B=100/A=000213
20260208190450DK4HPA-1>APRSGW,TCPIP*,qAR,DK4HPA-1:!5326.61N/01023.42E-Geesthacht#Peter E30/B=100/A=000213
20260208193505DK4HPA-1>APRSGW,TCPIP*,qAR,DK4HPA-1:!5326.61N/01023.42E-Geesthacht#Peter E30/B=100/A=000213
20260208200520DK4HPA-1>APRSGW,TCPIP*,qAR,DK4HPA-1:!5326.61N/01023.42E-Geesthacht#Peter E30/B=100/A=000213
20260208203539DK4HPA-1>APRSGW,TCPIP*,qAR,DK4HPA-1:!5326.61N/01023.42E-Geesthacht#Peter E30/B=100/A=000213