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
20251013150900NM5PB-13>APTEMP,TCPIP*,qAC,T2RDU:@080126z0000.00N/00000.00W_353/002g003t065r000p000P000h75b09860 aprs-tempest-2.0.0 Linux/x86_64
20251013152403NM5PB-13>APTEMP,TCPIP*,qAC,T2RDU:@080126z0000.00N/00000.00W_332/001g002t066r000p000P000h74b09860 aprs-tempest-2.0.0 Linux/x86_64
20251013153907NM5PB-13>APTEMP,TCPIP*,qAC,T2RDU:@080126z0000.00N/00000.00W_337/001g002t067r000p000P000h72b09860 aprs-tempest-2.0.0 Linux/x86_64
20251013155411NM5PB-13>APTEMP,TCPIP*,qAC,T2RDU:@080126z0000.00N/00000.00W_338/001g002t068r000p000P000h71b09860 aprs-tempest-2.0.0 Linux/x86_64
20251013170936NM5PB-13>APTEMP,TCPIP*,qAC,T2RDU:@080126z0000.00N/00000.00W_359/002g003t070r000p000P000h65b09870 aprs-tempest-2.0.0 Linux/x86_64