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
20260209152155N2TEK-1>APMI04,TCPIP*,qAS,N2TEK:@091522z3641.56NI07952.58W&PHG7030 MHC TX/RX IGATE/WX/Batt Backup 144.500
20260209155657N2TEK-1>APMI04,TCPIP*,qAS,N2TEK:@091557z3641.56NI07952.58W&PHG7030 MHC TX/RX IGATE/WX/Batt Backup 144.500
20260209163200N2TEK-1>APMI04,TCPIP*,qAS,N2TEK:@091632z3641.56NI07952.58W&PHG7030 MHC TX/RX IGATE/WX/Batt Backup 144.500
20260209170701N2TEK-1>APMI04,TCPIP*,qAS,N2TEK:@091707z3641.56NI07952.58W&PHG7030 MHC TX/RX IGATE/WX/Batt Backup 144.500
20260209174203N2TEK-1>APMI04,TCPIP*,qAS,N2TEK:@091742z3641.56NI07952.58W&PHG7030 MHC TX/RX IGATE/WX/Batt Backup 144.500
20260209181705N2TEK-1>APMI04,TCPIP*,qAS,N2TEK:@091817z3641.56NI07952.58W&PHG7030 MHC TX/RX IGATE/WX/Batt Backup 144.500
20260209185207N2TEK-1>APMI04,TCPIP*,qAS,N2TEK:@091852z3641.56NI07952.58W&PHG7030 MHC TX/RX IGATE/WX/Batt Backup 144.500
20260209192709N2TEK-1>APMI04,TCPIP*,qAS,N2TEK:@091927z3641.56NI07952.58W&PHG7030 MHC TX/RX IGATE/WX/Batt Backup 144.500
20260209200211N2TEK-1>APMI04,TCPIP*,qAS,N2TEK:@092002z3641.56NI07952.58W&PHG7030 MHC TX/RX IGATE/WX/Batt Backup 144.500
20260209203713N2TEK-1>APMI04,TCPIP*,qAS,N2TEK:@092037z3641.56NI07952.58W&PHG7030 MHC TX/RX IGATE/WX/Batt Backup 144.500