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
20180521072600SR3DPN>APMI06,qAR,SP3WBX:;1 T110 -060 1750 SR3P
20180521073805SR3DPN>APMI06,qAR,SP3WBX:;43 C110 -760 SR3PO
20180521081819SR3DPN>APMI06,SR3NPB,SR3NWY,WIDE2*,qAR,SP3WBX:!Poznan A=280
20180521102626SR3DPN>APMI06,qAR,SP3WBX:!5224.26NS01vp/; APRSISCE/32
20180521103811SR3DPN>APMI06,qAR,SP3WBX:;145.650-P*111111z5222 1750 SR3P
20180521113810SR3DPN>APMI06,WIDE2-2,qAR,SP3WBX:!52240 W2,SPn Poznan A=280
20180521120224SR3DPN>APMI06,qAR,SP3WBX:;43658.14E#PHG7140SQ3PLX ULARI Project with Direwolf