APRS Packet Errors for KA8MZJ (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
20190326112135KA8MZJ>APWW10,TCPIP*,qAC,T2DENMARK:@112135h4126.55N/08322.82W-PHG7260
20190326115135KA8MZJ>APWW10,TCPIP*,qAC,T2DENMARK:@115135h4126.55N/08322.82W-PHG7260
20190326122136KA8MZJ>APWW10,TCPIP*,qAC,T2DENMARK:@122135h4126.55N/08322.82W-PHG7260
20190326125135KA8MZJ>APWW10,TCPIP*,qAC,T2DENMARK:@125135h4126.55N/08322.82W-PHG7260
20190326132135KA8MZJ>APWW10,TCPIP*,qAC,T2DENMARK:@132135h4126.55N/08322.82W-PHG7260
20190326135135KA8MZJ>APWW10,TCPIP*,qAC,T2DENMARK:@135135h4126.55N/08322.82W-PHG7260
20190326142135KA8MZJ>APWW10,TCPIP*,qAC,T2DENMARK:@142134h4126.55N/08322.82W-PHG7260
20190326145135KA8MZJ>APWW10,TCPIP*,qAC,T2DENMARK:@145134h4126.55N/08322.82W-PHG7260
20190326152135KA8MZJ>APWW10,TCPIP*,qAC,T2DENMARK:@152134h4126.55N/08322.82W-PHG7260
20190326155135KA8MZJ>APWW10,TCPIP*,qAC,T2DENMARK:@155134h4126.55N/08322.82W-PHG7260
20190326162134KA8MZJ>APWW10,TCPIP*,qAC,T2DENMARK:@162134h4126.55N/08322.82W-PHG7260
20190326165134KA8MZJ>APWW10,TCPIP*,qAC,T2DENMARK:@165134h4126.55N/08322.82W-PHG7260