APRS Packet Errors for JH7MHZ-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
20260208140133	JH7MHZ-13>APK102,JE7ZGL-3,WIDE1*,qAR,7M3SKC-10:=4008.02N/14046.41E_305/000g t017r000p000P h92b09884KDvs
20260208150134	JH7MHZ-13>APK102,JE7ZGL-3,WIDE1*,qAR,7M3SKC-10:=4008.02N/14046.41E_156/000g t019r000p000P h93b09884KDvs
20260208160134	JH7MHZ-13>APK102,JE7ZGL-3,WIDE1*,qAR,7M3SKC-10:=4008.02N/14046.41E_105/000g t021r000p000P h94b09885KDvs
20260208180135	JH7MHZ-13>APK102,JE7ZGL-3,WIDE1*,qAR,JH7QJG:=4008.02N/14046.41E_353/000g t022r000p000P h86b09884KDvs
20260208190136	JH7MHZ-13>APK102,JE7ZGL-3,WIDE1*,qAR,7M3SKC-10:=4008.02N/14046.41E_269/000g t022r000p000P h88b09892KDvs