APRS Packet Errors for COR (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
20180521091623COR>APTT4,WIDE1-1,WID7,qAR,W4RMS-4:!34388704.82W_122/005g007t00p00P000073T
20180521093245COR>8DEU-7,qAR,W4RMS-4:!3.09N/08704W_136/0068t071r000000P001b1013
20180521095111COR>T4,WI-1,WI-1,qAS,W4RMS-4:!34339/0008t0000p0000h10174T
20180521120441COR>APTT4,WIDE1-1,WI7,qAR,W4RMS-4:!3438.09N/08704.8221/007g007t071rp000P000h81b101