APRS Packet Errors for SP6PTT-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
20180526075419SP6PTT-1>APRX28,SR3NWY,SR3NPB,WIDE2*,qAR,SP3WBX:;SR6TW *750MHz / 103.5Hz
20180526081230SP6PTT-1>APRX28,SR3NOW,SR3NWY,WIDE2*,qAR,SP3WBX:@111111z5120.40NI01729.67E
20180526082612SP6PTT-1>APRX28,SR3NOW,SR3NWY,WIDE2*,qAR,SP3WBX:@111111z5120.40NI01729.67E
20180526082936SP6PTT-1>APRX28,SR3NWY*,WIDE2-1,qAR,SP3WBX:;SR6TW *111111z5120.73N/017
20180526094129SP6PTT-1>APRX28,SR3NWY*,WIDE2-1,qAR,SP3WBX:;SR6TW *111111z5120.73N/0er Twardogora SR6TW 438.750MHz / 103.5Hz
20180526094133SP6PTT-1>APRX28,SR3NWY,SR3NPB,WIDE2*,qAR,SP3WBX:;SR6TW *111111z5120.73N