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
20171211170213SQ5NPP-1>APMI03,WIDE2-2,qAR,SR5ZU:;SQ5H-1 *111621z5222.43N/02042.21E- Heniek Augustowek
20171211170258SQ5NPP-1>APMI03,WIDE2-2,qAR,SR5ND:;SQ4K-1 *111622z5218.88N/02112.19E-Michal 145.400MHz
20171211180517SQ5NPP-1>APMI03,WIDE2-2,qAR,SR5ND:;SQ5H-1 *111724z5222.43N/02042.21E- Heniek Augustowek
20171211180702SQ5NPP-1>APMI03,WIDE2-2,qAR,SR5ZU:;SQ4K-1 *111726z5218.88N/02112.19E-Michal 145.400MHz
20171211190820SQ5NPP-1>APMI03,WIDE2-2,qAR,SR5ND:;SQ5H-1 *111827z5222.43N/02042.21E- Heniek Augustowek
20171211191106SQ5NPP-1>APMI03,WIDE2-2,qAR,SR5ZU:;SQ4K-1 *111830z5218.88N/02112.19E-Michal 145.400MHz
20171211201124SQ5NPP-1>APMI03,WIDE2-2,qAR,SR5ND:;SQ5H-1 *111930z5222.43N/02042.21E- Heniek Augustowek
20171211201509SQ5NPP-1>APMI03,WIDE2-2,qAR,SR5ND:;SQ4K-1 *111934z5218.88N/02112.19E-Michal 145.400MHz
20171211211427SQ5NPP-1>APMI03,WIDE2-2,qAR,SR5ZU:;SQ5H-1 *112033z5222.43N/02042.21E- Heniek Augustowek
20171211211912SQ5NPP-1>APMI03,WIDE2-2,qAR,SR5ND:;SQ4K-1 *112038z5218.88N/02112.19E-Michal 145.400MHz
20171211221732SQ5NPP-1>APMI03,WIDE2-2,qAR,SR5ZU:;SQ5H-1 *112136z5222.43N/02042.21E- Heniek Augustowek
20171211222316SQ5NPP-1>APMI03,WIDE2-2,qAR,SR5ND:;SQ4K-1 *112142z5218.88N/02112.19E-Michal 145.400MHz