APRS Packet Errors for DG1JAN-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
20260209132016DG1JAN-99>APRSMC,TCPIP*,qAR,DF2OO-7:!4936.20N/00635.71E-Meshcom GW JN39HO#Jan/A=000879
20260209135018DG1JAN-99>APRSMC,TCPIP*,qAR,DF2OO-7:!4936.20N/00635.71E-Meshcom GW JN39HO#Jan/A=000879
20260209142012DG1JAN-99>APRSMC,TCPIP*,qAR,DF2OO-7:!4936.20N/00635.71E-Meshcom GW JN39HO#Jan/A=000879
20260209145018DG1JAN-99>APRSMC,TCPIP*,qAR,DF2OO-7:!4936.20N/00635.71E-Meshcom GW JN39HO#Jan/A=000879
20260209152018DG1JAN-99>APRSMC,TCPIP*,qAR,DF2OO-7:!4936.20N/00635.71E-Meshcom GW JN39HO#Jan/A=000879
20260209155012DG1JAN-99>APRSMC,TCPIP*,qAR,DF2OO-7:!4936.20N/00635.71E-Meshcom GW JN39HO#Jan/A=000879
20260209162028DG1JAN-99>APRSMC,TCPIP*,qAR,DF2OO-7:!4936.20N/00635.71E-Meshcom GW JN39HO#Jan/A=000879
20260209165019DG1JAN-99>APRSMC,TCPIP*,qAR,DF2OO-7:!4936.20N/00635.71E-Meshcom GW JN39HO#Jan/A=000879
20260209172018DG1JAN-99>APRSMC,TCPIP*,qAR,DF2OO-7:!4936.20N/00635.71E-Meshcom GW JN39HO#Jan/A=000879
20260209175018DG1JAN-99>APRSMC,TCPIP*,qAR,DF2OO-7:!4936.20N/00635.71E-Meshcom GW JN39HO#Jan/A=000879
20260209182018DG1JAN-99>APRSMC,TCPIP*,qAR,DF2OO-7:!4936.20N/00635.71E-Meshcom GW JN39HO#Jan/A=000879
20260209185021DG1JAN-99>APRSMC,TCPIP*,qAR,DF2OO-7:!4936.20N/00635.71E-Meshcom GW JN39HO#Jan/A=000879