APRS Packet Errors for DL1EEN-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
20260208134004DL1EEN-12>APRSMC,TCPIP*,qAR,DL1EEN-20:!5007.64N/00642.72E##Norbert/B=100/A=001440
20260208141157DL1EEN-12>APRSMC,TCPIP*,qAR,DL1EEN-20:!5007.67N/00642.70E##Norbert/B=100/A=001414
20260208142449DL1EEN-12>APRSMC,TCPIP*,qAR,DL1EEN-20:!5007.67N/00642.70E##Norbert/B=100/A=001293
20260208145503DL1EEN-12>APRSMC,TCPIP*,qAR,DL1EEN-20:!5007.64N/00642.73E##Norbert/B=100/A=001568
20260208152511DL1EEN-12>APRSMC,TCPIP*,qAR,DL1EEN-20:!5007.67N/00642.74E##Norbert/B=100/A=001568
20260208155526DL1EEN-12>APRSMC,TCPIP*,qAR,DL1EEN-20:!5007.64N/00642.72E##Norbert/B=100/A=001549
20260208162541DL1EEN-12>APRSMC,TCPIP*,qAR,DL1EEN-20:!5007.66N/00642.73E##Norbert/B=100/A=001581
20260208170138DL1EEN-12>APRSMC,TCPIP*,qAR,DL1EEN-20:!5007.64N/00642.73E##Norbert/B=100/A=001591
20260208174857DL1EEN-12>APRSMC,TCPIP*,qAR,DL1EEN-20:!5007.65N/00642.73E##Norbert/B=100/A=001516
20260208180807DL1EEN-12>APRSMC,TCPIP*,qAR,DL1EEN-20:!5007.65N/00642.73E##Norbert/B=100/A=001526
20260208183928DL1EEN-12>APRSMC,TCPIP*,qAR,DL1EEN-20:!5007.64N/00642.73E##Norbert/B=100/A=001522
20260208191009DL1EEN-12>APRSMC,TCPIP*,qAR,DL1EEN-20:!5007.65N/00642.73E##Norbert/B=100/A=001654