APRS Packet Errors for SR3DPN (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
20180522121459SR3DPN>APMI06,SR3NWY*,WIDE2-1,qAR,SP3WBX:!5224.26NS01655.64E
20180522123942SR3DPN>APMI06,qAR,SP3WBX:;145.650-P*10 1750 SR3P
20180522135442SR3DPN>APMI06,WIDE2-2,qAR,SP3WBX:!5224.26NS0165
20180522135758SR3DPN>APMI06,qAR,SP3WBX:;1fd@讒b@
20180522140902SR3DPN>APMI06,qAR,SP3WBX:;145.762-X*111111z522
20180522141553SR3DPN>APMI06,qAR,SP3WBX:;111111z5224.06N/01655.56Er439.200MHz C110 -760 SR3PO
20180522143104SR3DPN>APMI06,qAR,SP3WBX:!52E01652.66E0145.337MHz T067 Rawicz op.SP3PDK
20180522143955SR3DPN>APMI06,qAR,SP3WBX:;439.200-P*111111z5224.
20180522144444SR3DPN>APMI06,WIDE2-2,qAR,SP3WBX:!5224.26NS0165
20180522150946SR3DPN>APMI06,SR3NPB*,WIDE2-1,qAR,SP3WBX:!5224.26NS01655.64E
20180522155949SR3DPN>APMI06,WIDE2-2,qAR,SP3WBX:!5224.26NS01655
20180522161004SR3DPN>APMI06,qAR,SP3WBX:;145.762-X*11 C110 -060 SR3X
20180522162757SR3DPN>APMI06,qAR,SP3WBX:;145.650-P*111111z5222
20180522163955SR3DPN>APMI06,qAR,SP3WBX:;14 1750 SR3P
20180522164312SR3DPN>APMI06,qAR,SP3WBX:!5224.26NS016
20180522164952SR3DPN>APMI06,WIDE2-2,qAR,SP3WBX:!5224.26NS01655.
20180522173814SR3DPN>APMI06,qAR,SP3WBX:;145.762-X*111111z522