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
20190521114903HB0AA>APU25N,HB9BB,WIDE3-2,qAR,OE9XVI:@211149z/6Z!7Pt+"_!!bg000t056r001p003P066h99b10203 asl 456 {UIV32N}
20190521120903HB0AA>APU25N,HB9BB,WIDE3-2,qAR,OE9XVI:@211209z/6Z!7Pt+"_!!bg000t056r001p002P066h99b10205 asl 456 {UIV32N}
20190521122903HB0AA>APU25N,HB9BB,WIDE3-2,qAR,OE9XVI:@211229z/6Z!7Pt+"_!!bg000t056r000p002P066h99b10205 asl 456 {UIV32N}
20190521124903HB0AA>APU25N,HB9BB,WIDE3-2,qAR,OE9XVI:@211249z/6Z!7Pt+"_!!bg000t056r000p002P066h99b10208 asl 456 {UIV32N}
20190521130904HB0AA>APU25N,HB9BB,WIDE3-2,qAR,OE9XVI:@211309z/6Z!7Pt+"_!!bg000t056r001p003P067h99b10210 asl 456 {UIV32N}
20190521132903HB0AA>APU25N,HB9BB,WIDE3-2,qAR,OE9XVI:@211329z/6Z!7Pt+"_!!bg001t055r001p003P067h99b10210 asl 456 {UIV32N}
20190521134904HB0AA>APU25N,HB9BB,WIDE3-2,qAR,OE9XVI:@211349z/6Z!7Pt+"_!!bg002t055r001p003P067h99b10212 asl 456 {UIV32N}
20190521140903HB0AA>APU25N,HB9BB,WIDE3-2,qAR,OE9XVI:@211409z/6Z!7Pt+"_!!bg000t055r000p003P067h99b10215 asl 456 {UIV32N}
20190521142903HB0AA>APU25N,HB9BB,WIDE3-2,qAR,OE9XVI:@211429z/6Z!7Pt+"_!!bg002t055r001p004P068h99b10215 asl 456 {UIV32N}
20190521144903HB0AA>APU25N,HB9BB,WIDE3-2,qAR,OE9XVI:@211449z/6Z!7Pt+"_!!bg001t055r001p004P068h99b10218 asl 456 {UIV32N}