APRS Packet Errors for DL1HCI-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
20260209130751DL1HCI-99>APRSMC,TCPIP*,qAR,DL1HCI-12:!5326.96NM01004.08E#MeshComNode/B=100/A=000023
20260209133812DL1HCI-99>APRSMC,TCPIP*,qAR,DL1HCI-12:!5326.96NM01004.08E#MeshComNode/B=100
20260209140829DL1HCI-99>APRSMC,TCPIP*,qAR,DL1HCI-12:!5326.96NM01004.08E#MeshComNode/B=100
20260209143849DL1HCI-99>APRSMC,TCPIP*,qAR,DL1HCI-12:!5326.96NM01004.08E#MeshComNode/B=100
20260209150909DL1HCI-99>APRSMC,TCPIP*,qAR,DL1HCI-12:!5326.96NM01004.08E#MeshComNode/B=100
20260209153929DL1HCI-99>APRSMC,TCPIP*,qAR,DL1HCI-12:!5326.96NM01004.07E#MeshComNode/B=100
20260209160940DL1HCI-99>APLT00-1,WIDE1-1,qAO,DC5HB-16:=M3L?5Q$TQ# P[
20260209160952DL1HCI-99>APRSMC,TCPIP*,qAR,DL1HCI-12:!5326.96NM01004.09E#MeshComNode/B=100
20260209164005DL1HCI-99>APRSMC,TCPIP*,qAR,DL1HCI-12:!5326.96NM01004.08E#MeshComNode/B=100
20260209171015DL1HCI-99>APRSMC,TCPIP*,qAR,DL1HCI-12:!5326.96NM01004.09E#MeshComNode/B=100
20260209174030DL1HCI-99>APRSMC,TCPIP*,qAR,DL1HCI-12:!5326.96NM01004.08E#MeshComNode/B=100
20260209181045DL1HCI-99>APRSMC,TCPIP*,qAR,DL1HCI-12:!5326.96NM01004.07E#MeshComNode/B=100
20260209184100DL1HCI-99>APRSMC,TCPIP*,qAR,DL1HCI-12:!5326.96NM01004.08E#MeshComNode/B=100