APRS Packet Errors for HB0AA (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
20180324155900HB0AA>APU25N,HB9BB*,WIDE3-2,qAR,OE9IMJ-10:@241558z/6Z!7Pt+"_)!bg004t062r000p000P000h26b09902 asl 456 {UIV32N}
20180324161900HB0AA>APU25N,HB9BB*,WIDE3-2,qAR,OE9IMJ-10:@241618z/6Z!7Pt+"_%!bg005t061r000p000P000h26b09903 asl 456 {UIV32N}
20180324163858HB0AA>APU25N,HB9BB,WIDE3-2,qAR,DB0WV-10:@241638z/6Z!7Pt+"_)!bg003t061r000p000P000h24b09906 asl 456 {UIV32N}
20180324165858HB0AA>APU25N,HB9BB,WIDE3-2,qAR,DB0WV-10:@241658z/6Z!7Pt+"_)!bg004t059r000p000P000h25b09910 asl 456 {UIV32N}
20180324175900HB0AA>APU25N,HB9BB*,WIDE3-2,qAR,OE9IMJ-10:@241758z/6Z!7Pt+"_!!bg001t044r000p000P000h67b09916 asl 456 {UIV32N}
20180324183859HB0AA>APU25N,HB9BB,WIDE3-2,qAR,DB0WV-10:@241838z/6Z!7Pt+"_!!bg000t042r000p000P000h69b09919 asl 456 {UIV32N}