APRS Packet Errors for DG0JJH-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
20260209094619DG0JJH-12>APRSGW,TCPIP*,qAR,DG0JJH-12:!5044.85NL01304.66E&#Meshcom Gateway/A=001181
20260209101619DG0JJH-12>APRSGW,TCPIP*,qAR,DG0JJH-12:!5044.85NL01304.66E&#Meshcom Gateway/A=001191
20260209104619DG0JJH-12>APRSGW,TCPIP*,qAR,DG0JJH-12:!5044.84NL01304.67E&#Meshcom Gateway/A=001175
20260209111619DG0JJH-12>APRSGW,TCPIP*,qAR,DG0JJH-12:!5044.84NL01304.66E&#Meshcom Gateway/A=001188
20260209114620DG0JJH-12>APRSGW,TCPIP*,qAR,DG0JJH-12:!5044.85NL01304.66E&#Meshcom Gateway/A=001325
20260209121620DG0JJH-12>APRSGW,TCPIP*,qAR,DG0JJH-12:!5044.86NL01304.66E&#Meshcom Gateway/A=001276
20260209124620DG0JJH-12>APRSGW,TCPIP*,qAR,DG0JJH-12:!5044.84NL01304.66E&#Meshcom Gateway/A=001201
20260209131620DG0JJH-12>APRSGW,TCPIP*,qAR,DG0JJH-12:!5044.84NL01304.66E&#Meshcom Gateway/A=001155
20260209134620DG0JJH-12>APRSGW,TCPIP*,qAR,DG0JJH-12:!5044.84NL01304.66E&#Meshcom Gateway/A=001161
20260209141620DG0JJH-12>APRSGW,TCPIP*,qAR,DG0JJH-12:!5044.84NL01304.66E&#Meshcom Gateway/A=001168
20260209144621DG0JJH-12>APRSGW,TCPIP*,qAR,DG0JJH-12:!5044.84NL01304.66E&#Meshcom Gateway/A=001178
20260209151621DG0JJH-12>APRSGW,TCPIP*,qAR,DG0JJH-12:!5044.86NL01304.66E&#Meshcom Gateway/A=001204