APRS Packet Errors for SP3QYJ (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
20180528001036SP3QYJ>APK102,WIDE1-1,WIDE2-1,qAR,SP3WBX:=5138.11N/01654.19E
20180528001052SP3QYJ>APK102,SR3NWY,WIDE1*,WIDE2-1,qAR,SP3WBX:=5138.11N/00h73b10045KU2k
20180528013208SP3QYJ>APK102,SR6NWS,WIDE1,SR3NWY,WIDE2*,qAR,SP3WBX:=513878b10045KU2k
20180528015148SP3QYJ>APK102,SR6NDZ,WIDE1*,WIDE2-1,qAR,SP3WBX:=5138.11N/01654.19E_0
20180528021215SP3QYJ>APK102,SR3NWY,WIDE1*,WIDE2-1,qAR,SP3WBX:=5138.11N/.11N/01654.19E_000/000g000t064r p P000h79b10045KU2k
20180528022239SP3QYJ>APK102,SR6NWS,WIDE1*,WIDE2-1,qAR,SP3WBX:=5138.11N/016
20180528025304SP3QYJ>APK102,SR6NWS,WIDE1,SP3AH,SR3NPB,SR3NJE,WIDE2*,qAR,SP3WBX:=5138.11N/0165
20180528031439SP3QYJ>APK102,SR6NWS,WIDE1*,WIDE2-1,qAR,SP3WBX:=5138.11N/01654.19E_000/00
20180528031446SP3QYJ>APK102,SR6NWS,WIDE1,SR3NZG,WIDE2*,qAR,SP3WBX:=5138.11N/016541b10045KU2k
20180528041423SP3QYJ>APK102,SR6NDZ,WIDE1*,WIDE2-1,qAR,SP3WBX:=5r p P000h78b10046KU2k
20180528043440SP3QYJ>APK102,SR6NDZ,WIDE1,SP3AH,SR3NPB,SR3DPN,WIDE2*,qAR,SP3WBX:=5138.11N/01654.19E_000/