APRS Packet Errors for JA6XZK-13 (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
20260209162021JA6XZK-13>API905,DSTAR*,qAS,JR3VE-IS:/162019h3440.70N/13534.33E-PHG0494/A=000187Auto
20260209165022JA6XZK-13>API905,DSTAR*,qAS,JR3VE-IS:/165020h3440.70N/13534.33E-PHG0494/A=000187Auto
20260209172023JA6XZK-13>API905,DSTAR*,qAS,JR3VE-IS:/172021h3440.70N/13534.33E-PHG0494/A=000187Auto
20260209175024JA6XZK-13>API905,DSTAR*,qAS,JR3VE-IS:/175022h3440.70N/13534.33E-PHG0494/A=000187Auto
20260209182025JA6XZK-13>API905,DSTAR*,qAS,JR3VE-IS:/182023h3440.70N/13534.33E-PHG0494/A=000187Auto
20260209185026JA6XZK-13>API905,DSTAR*,qAS,JR3VE-IS:/185024h3440.70N/13534.33E-PHG0494/A=000187Auto
20260209192027JA6XZK-13>API905,DSTAR*,qAS,JR3VE-IS:/192025h3440.70N/13534.33E-PHG0494/A=000187Auto
20260209195028JA6XZK-13>API905,DSTAR*,qAS,JR3VE-IS:/195026h3440.70N/13534.33E-PHG0494/A=000187Auto
20260209202029JA6XZK-13>API905,DSTAR*,qAS,JR3VE-IS:/202027h3440.70N/13534.33E-PHG0494/A=000187Auto
20260209205030JA6XZK-13>API905,DSTAR*,qAS,JR3VE-IS:/205028h3440.70N/13534.33E-PHG0494/A=000187Auto
20260209212031JA6XZK-13>API905,DSTAR*,qAS,JR3VE-IS:/212029h3440.70N/13534.33E-PHG0494/A=000187Auto
20260209215032JA6XZK-13>API905,DSTAR*,qAS,JR3VE-IS:/215030h3440.70N/13534.33E-PHG0494/A=000187Auto