APRS Packet Errors for SR3NOW (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
20180520141725SR3NOW>APMI06,SR3NWY*,WIDE2-1,qAR,SP3WBX:@201505zd@`-L|l 0>`"50}433.550MHz Henryk _(
20180520142742SR3NOW>APMI06,SR3NWY,SR3NPB,WIDE2*,qAR,SP3WBX:@201515z5139.57N/01747I
20180520143735SR3NOW>APMI06,SR3NWY,SR3NPB,WIDE2*,qAR,SP3WBX:@201525z5139.57N/01747.79E
20180520155741SR3NOW>APMI06,SR3NWY,SR3NPB,WIDE2*,qAR,SP3WBX:@201645z51d@@272332z5237.22N/01803.12E_022/000g000t074r000p000P...h43b10229Kwieciszewo
20180520162742SR3NOW>APMI06,SR3NWY*,WIDE2-1,qAR,SP3WBX:@201715z5139.57N/01
20180520185237SR3NOW>APMI06,SR3NWY*,WIDE2-1,qAR,SP3WBX:@201940z5139.57N/01