APRS Packet Errors for HATSCH (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
20170501020257HATSCH>APOT2A,AL1-1,qAR,KG4PID-14:!3433.66N/08724.97W_179/│15g...tC53PŘ03h95b46003T2WX
20170501031053HATSCH>APOT2A,AL1-1,qAR,KG4PID-14:!3433.66N/08724.97W_179/│15g...tC53PŘ03h95b46003T2WX
20170501032637HATSCH>APOT2A,AL1-1,qAR,KG4PID-14:!3433.66N/08724.97W_179/│15g...tC53PŘ03h95b46003T2WX
20170501034132HATSCH>APOT2A,AL1-1,qAR,KG4PID-14:!3433.66N/08724.97W_179/│15g...tC53PŘ03h95b46003T2WX
20170501035628HATSCH>APOT2A,AL1-1,qAR,KG4PID-14:!3433.66N/08724.97W_179/│15g...tC53PŘ03h95b46003T2WX
20170501040354HATSCH>APOT2A,AL1-1,qAR,KG4PID-14:!3433.66N/08724.97W_179/│15g...tC53PŘ03h95b46003T2WX
20170501043435HATSCH>APOT2A,AL1-1,qAR,KG4PID-14:!3433.66N/08724.97W_179/│15g...tC53PŘ03h95b46003T2WX
20170501044932HATSCH>APOT2A,AL1-1,qAR,KG4PID-14:!3433.66N/08724.97W_179/│15g...tC53PŘ03h95b46003T2WX
20170501051924HATSCH>APOT2A,AL1-1,qAR,KG4PID-14:!3433.66N/08724.97W_179/│15g...tC53PŘ03h95b46003T2WX
20170501053509HATSCH>APOT2A,AL1-1,qAR,KG4PID-14:!3433.66N/08724.97W_179/│15g...tC53PŘ03h95b46003T2WX
20170501055006HATSCH>APOT2A,AL1-1,qAR,KG4PID-14:!3433.66N/08724.97W_179/│15g...tC53PŘ03h95b46003T2WX
20170501055734HATSCH>APOT2A,AL1-1,qAR,KG4PID-14:!3433.66N/08724.97W_179/│15g...tC53PŘ03h95b46003T2WX