APRS Packet Errors for N2TEK-1 (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
20260208134028N2TEK-1>APMI04,TCPIP*,qAS,N2TEK:@081340z3641.56NI07952.58W&PHG7030 MHC TX/RX IGATE/WX/Batt Backup 144.500
20260208141530N2TEK-1>APMI04,TCPIP*,qAS,N2TEK:@081415z3641.56NI07952.58W&PHG7030 MHC TX/RX IGATE/WX/Batt Backup 144.500
20260208145032N2TEK-1>APMI04,TCPIP*,qAS,N2TEK:@081450z3641.56NI07952.58W&PHG7030 MHC TX/RX IGATE/WX/Batt Backup 144.500
20260208152534N2TEK-1>APMI04,TCPIP*,qAS,N2TEK:@081525z3641.56NI07952.58W&PHG7030 MHC TX/RX IGATE/WX/Batt Backup 144.500
20260208160036N2TEK-1>APMI04,TCPIP*,qAS,N2TEK:@081600z3641.56NI07952.58W&PHG7030 MHC TX/RX IGATE/WX/Batt Backup 144.500
20260208163538N2TEK-1>APMI04,TCPIP*,qAS,N2TEK:@081635z3641.56NI07952.58W&PHG7030 MHC TX/RX IGATE/WX/Batt Backup 144.500
20260208171040N2TEK-1>APMI04,TCPIP*,qAS,N2TEK:@081710z3641.56NI07952.58W&PHG7030 MHC TX/RX IGATE/WX/Batt Backup 144.500
20260208174542N2TEK-1>APMI04,TCPIP*,qAS,N2TEK:@081745z3641.56NI07952.58W&PHG7030 MHC TX/RX IGATE/WX/Batt Backup 144.500
20260208182044N2TEK-1>APMI04,TCPIP*,qAS,N2TEK:@081820z3641.56NI07952.58W&PHG7030 MHC TX/RX IGATE/WX/Batt Backup 144.500
20260208185546N2TEK-1>APMI04,TCPIP*,qAS,N2TEK:@081855z3641.56NI07952.58W&PHG7030 MHC TX/RX IGATE/WX/Batt Backup 144.500