APRS Packet Errors for SR1NRW (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
20180527233323SR1NRW>APNX03,SR3NPB,WIDE2*,qAR,SP3WBX:;439.400-W*111111z5
20180527233324SR1NRW>APNX03,SP3AH,SR3NZG,SR3NRI,WIDE2*,qAR,SP3WBX:;439.400-W*111111z5316.68N/0C082 -760 SR1WA
20180528000421SR1NRW>APNX03,SR3NWY,SR3NPB,WIDE2*,qAR,SP3WBX:!0 W2, SPn digi Walcz, op. SQ1GQN
20180528003353SR1NRW>APNX03,SR3NPB*,WIDE2-1,qAR,SP3WBX:!5316.76NS01628.96alcz, op. SQ1GQN
20180528013417SR1NRW>APNX03,SR3NWY,SR3NPB,WIDE2*,qAR,SP3WBX:!5316.76NS016
20180528021335SR1NRW>APNX03,SR3NZG,WIDE2*,qAR,SP3WBX:;439.400-5339.27N/01722.16E_090/008g008t060r000p000P...h89b10231SR2WXCZ Czluchow
20180528030337SR1NRW>APNX03,SR3NPB,WIDE2*,qAR,SP3WBX:;439.400
20180528041342SR1NRW>APNX03,SR3NPB,WIDE2*,qAR,SP3WBX:;439.40
20180528041350SR1NRW>APNX03,SR3NZG,WIDE2*,qAR,SP3WBX:;439.400- SLUPSK
20180528043416SR1NRW>APNX03,SR3NPB*,WIDE2-1,qAR,SP3WBX:!5316.76NS01628.96E
20180528045345SR1NRW>APNX03,SR3NPB,WIDE2*,qAR,SP3WBX:;439.400-
20180528051350SR1NRW>APNX03,SR3NJE,WIDE2*,qAR,SP3WBX:;439.400760 SR1WA