APRS Packet Errors for NM5PB-13 (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
20251013211042NM5PB-13>APTEMP,TCPIP*,qAC,T2RDU:@080126z0000.00N/00000.00W_321/001g001t074r000p000P000h56b09870 aprs-tempest-2.0.0 Linux/x86_64
20251013212546NM5PB-13>APTEMP,TCPIP*,qAC,T2RDU:@080126z0000.00N/00000.00W_325/001g001t074r000p000P000h52b09870 aprs-tempest-2.0.0 Linux/x86_64
20251013231112NM5PB-13>APTEMP,TCPIP*,qAC,T2RDU:@080126z0000.00N/00000.00W_008/000g001t068r000p000P000h68b09880 aprs-tempest-2.0.0 Linux/x86_64
20251013232615NM5PB-13>APTEMP,TCPIP*,qAC,T2RDU:@080126z0000.00N/00000.00W_032/000g000t067r000p000P000h70b09890 aprs-tempest-2.0.0 Linux/x86_64
20251013234118NM5PB-13>APTEMP,TCPIP*,qAC,T2RDU:@080126z0000.00N/00000.00W_004/000g000t065r000p000P000h73b09890 aprs-tempest-2.0.0 Linux/x86_64