APRS Packet Errors for M9YJR (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
20251026221544M9YJR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M9YJR-DP!5147.85N/000-47.00rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000@+4.8 MHz
20251026224728M9YJR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M9YJR-DP!5147.85N/000-47.00rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000@+4.8 MHz
20251026231911M9YJR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M9YJR-DP!5147.85N/000-47.00rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000@+4.8 MHz
20251026235054M9YJR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M9YJR-DP!5147.85N/000-47.00rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000@+4.8 MHz
20251027002238M9YJR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M9YJR-DP!5147.85N/000-47.00rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000@+4.8 MHz
20251027005422M9YJR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M9YJR-DP!5147.85N/000-47.00rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000@+4.8 MHz
20251027012603M9YJR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M9YJR-DP!5147.85N/000-47.00rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000@+4.8 MHz
20251027030104M9YJR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M9YJR-DP!5147.85N/000-47.00rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000@+4.8 MHz
20251027040425M9YJR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M9YJR-DP!5147.85N/000-47.00rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000@+4.8 MHz