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
20170625132106HB0AA>APU25N,WIDE3-3,qAR,HB9BB:@251321z/6Z!7Pt+"_!!bg000t080r000p015P012h61b10145 asl 456 {UIV32N}
20170625134106HB0AA>APU25N,WIDE3-3,qAR,HB9BB:@251341z/6Z!7Pt+"_!!bg001t085r000p015P012h49b10140 asl 456 {UIV32N}
20170625140106HB0AA>APU25N,WIDE3-3,qAR,HB9BB:@251401z/6Z!7Pt+"_!!bg000t085r000p015P012h51b10140 asl 456 {UIV32N}
20170625142107HB0AA>APU25N,WIDE3-3,qAR,HB9BB:@251421z/6Z!7Pt+"_!!bg000t089r000p015P012h42b10137 asl 456 {UIV32N}
20170625144107HB0AA>APU25N,WIDE3-3,qAR,HB9BB:@251441z/6Z!7Pt+"_!!bg000t089r000p015P012h43b10135 asl 456 {UIV32N}
20170625150107HB0AA>APU25N,WIDE3-3,qAR,HB9BB:@251501z/6Z!7Pt+"_+!bg003t090r000p015P012h42b10132 asl 456 {UIV32N}
20170625152105HB0AA>APU25N,WIDE3-3,qAR,HB9BB:@251521z/6Z!7Pt+"_()bg005t085r000p015P012h45b10132 asl 456 {UIV32N}