APRS Packet Errors for SQ3HVZ-9 (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
20180521070200SQ3HVZ-9>APWM10,SR3DPN,WIDE1,SR3NWY,WIDE2*,qAR,SP3WBX:=5225emowit loc rpt 145.550 Mhz. 433,500 Mhz
20180521075404SQ3HVZ-9>APWM10,SR3NPB,WIDE1,SR3NWY,WIDE2*,qAR,SP3WBX:=5222.91N1645.59E
20180521080859SQ3HVZ-9>APWM10,SP3LOZ*,WIDE2-1,qAR,SP3WBX:=5221.13N1659.80 Mhz
20180521083255SQ3HVZ-9>APWM10,WIDE1-1,WIDE2-1,qAR,SP3WBX:=5222.76N1656.7
20180521085411SQ3HVZ-9>APWM10,SP3YEE,WIDE1,SR3NWY,WIDE2*,qAR,SP3WBX:=5222fஒd@`,TPl!K>"4i}Rob QRV 500 loc rpt
20180521103530SQ3HVZ-9>APWM10,SP3LOZ*,WIDE2-1,qAR,SP3WBX:=5222.41NMhz. 433,500 Mhz
20180521114154SQ3HVZ-9>APWM10,SP3LOZ*,WIDE2-1,qAR,SP3WBX:=5223.0241Ziemowit loc rpt 145.550 Mhz. 433,500 Mhz
20180521114704SQ3HVZ-9>APWM10,SR3NPB,WIDE1*,WIDE2-1,qAR,SP3WBX:=57Ziemowit loc rpt 145.550 Mhz. 433,500 Mhz
20180521115137SQ3HVZ-9>APWM10,SP3YEE,WIDE1,SR3NPB,WIDE2*,qAR,SP3WBX:=5218.97N17