APRS Packet Errors for DL1EEN-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
20260209094059DL1EEN-20>APRSGW,TCPIP*,qAR,DL1EEN-20:!5007.64N/00642.72E##Norbert/B=100/A=001709
20260209101117DL1EEN-20>APRSGW,TCPIP*,qAR,DL1EEN-20:!5007.64N/00642.72E##Norbert/B=100/A=001709
20260209104132DL1EEN-20>APRSGW,TCPIP*,qAR,DL1EEN-20:!5007.64N/00642.72E##Norbert/B=100/A=001709
20260209111147DL1EEN-20>APRSGW,TCPIP*,qAR,DL1EEN-20:!5007.64N/00642.72E##Norbert/B=100/A=001709
20260209114202DL1EEN-20>APRSGW,TCPIP*,qAR,DL1EEN-20:!5007.64N/00642.72E##Norbert/B=100/A=001709
20260209121217DL1EEN-20>APRSGW,TCPIP*,qAR,DL1EEN-20:!5007.64N/00642.72E##Norbert/B=100/A=001709
20260209124233DL1EEN-20>APRSGW,TCPIP*,qAR,DL1EEN-20:!5007.64N/00642.72E##Norbert/B=100/A=001709
20260209131248DL1EEN-20>APRSGW,TCPIP*,qAR,DL1EEN-20:!5007.64N/00642.72E##Norbert/B=100/A=001709
20260209134303DL1EEN-20>APRSGW,TCPIP*,qAR,DL1EEN-20:!5007.64N/00642.72E##Norbert/B=100/A=001709
20260209141318DL1EEN-20>APRSGW,TCPIP*,qAR,DL1EEN-20:!5007.64N/00642.72E##Norbert/B=100/A=001709
20260209144333DL1EEN-20>APRSGW,TCPIP*,qAR,DL1EEN-20:!5007.64N/00642.72E##Norbert/B=100/A=001709
20260209151348DL1EEN-20>APRSGW,TCPIP*,qAR,DL1EEN-20:!5007.64N/00642.72E##Norbert/B=100/A=001709