APRS Packet Errors for SQ5NPP-1 (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
20171020173914SQ5NPP-1>APMI03,WIDE2-2,qAR,SR5ZU:;SQ4K-1 *201700z5218.88N/02112.19E-Michal 145.400MHz
20171020182632SQ5NPP-1>APMI03,WIDE2-2,qAR,SR5ZU:;SQ5H-1 *201747z5222.43N/02042.21E- Heniek Augustowek
20171020192936SQ5NPP-1>APMI03,WIDE2-2,qAR,SR7NWL-10:;SQ5H-1 *201850z5222.43N/02042.21E- Heniek Augustowek
20171020194722SQ5NPP-1>APMI03,WIDE2-2,qAR,SR5ZU:;SQ4K-1 *201908z5218.88N/02112.19E-Michal 145.400MHz
20171020203239SQ5NPP-1>APMI03,WIDE2-2,qAR,SR5ZU:;SQ5H-1 *201953z5222.43N/02042.21E- Heniek Augustowek
20171020205125SQ5NPP-1>APMI03,WIDE2-2,qAR,SR7NWL-10:;SQ4K-1 *202012z5218.88N/02112.19E-Michal 145.400MHz
20171020215529SQ5NPP-1>APMI03,WIDE2-2,qAR,SQ5LTL:;SQ4K-1 *202116z5218.88N/02112.19E-Michal 145.400MHz
20171020223846SQ5NPP-1>APMI03,WIDE2-2,qAR,SR5ZU:;SQ5H-1 *202159z5222.43N/02042.21E- Heniek Augustowek
20171020225932SQ5NPP-1>APMI03,WIDE2-2,qAR,SR5ZU:;SQ4K-1 *202220z5218.88N/02112.19E-Michal 145.400MHz