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
20181212034955HB0AA>APU25N,HB9BB,WIDE3-2,qAR,OE9XVI:@120349z/6Z!7Pt+"_!!bg000t026r000p003P000h97b10115 asl 456 {UIV32N}
20181212040955HB0AA>APU25N,HB9BB,WIDE3-2,qAR,OE9XVI:@120409z/6Z!7Pt+"_!!bg000t026r000p003P000h96b10112 asl 456 {UIV32N}
20181212042955HB0AA>APU25N,HB9BB,WIDE3-2,qAR,OE9XVI:@120429z/6Z!7Pt+"_!!bg000t025r000p003P000h97b10113 asl 456 {UIV32N}
20181212044955HB0AA>APU25N,HB9BB,WIDE3-2,qAR,OE9XVI:@120449z/6Z!7Pt+"_!!bg000t025r000p003P000h96b10113 asl 456 {UIV32N}
20181212050956HB0AA>APU25N,HB9BB,WIDE3-2,qAR,OE9XVI:@120509z/6Z!7Pt+"_!!bg000t025r000p003P000h97b10113 asl 456 {UIV32N}
20181212052955HB0AA>APU25N,HB9BB,WIDE3-2,qAR,OE9XVI:@120529z/6Z!7Pt+"_!!bg000t025r000p003P000h97b10115 asl 456 {UIV32N}
20181212054955HB0AA>APU25N,HB9BB,WIDE3-2,qAR,OE9XVI:@120549z/6Z!7Pt+"_!!bg000t024r000p003P000h96b10115 asl 456 {UIV32N}
20181212060956HB0AA>APU25N,HB9BB,WIDE3-2,qAR,OE9XVI:@120609z/6Z!7Pt+"_!!bg000t025r000p003P000h95b10112 asl 456 {UIV32N}
20181212062955HB0AA>APU25N,HB9BB,WIDE3-2,qAR,OE9XVI:@120629z/6Z!7Pt+"_!!bg000t024r000p003P000h95b10115 asl 456 {UIV32N}
20181212064955HB0AA>APU25N,HB9BB,WIDE3-2,qAR,OE9XVI:@120649z/6Z!7Pt+"_!!bg000t024r000p003P000h95b10115 asl 456 {UIV32N}