APRS Packet Errors for M0BOY (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
20250417150140M0BOY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0BOY-DP!5200.64N/000-46.62rRNG0034 IPSC2-DVSPh-F MMDVM 438.8750@-8.0 MHz
20250417153353M0BOY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0BOY-DP!5200.64N/000-46.62rRNG0034 IPSC2-DVSPh-F MMDVM 438.8750@-8.0 MHz
20250417160550M0BOY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0BOY-DP!5200.64N/000-46.62rRNG0034 IPSC2-DVSPh-F MMDVM 438.8750@-8.0 MHz
20250417163745M0BOY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0BOY-DP!5200.64N/000-46.62rRNG0034 IPSC2-DVSPh-F MMDVM 438.8750@-8.0 MHz
20250417170938M0BOY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0BOY-DP!5200.64N/000-46.62rRNG0034 IPSC2-DVSPh-F MMDVM 438.8750@-8.0 MHz
20250417174132M0BOY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0BOY-DP!5200.64N/000-46.62rRNG0034 IPSC2-DVSPh-F MMDVM 438.8750@-8.0 MHz
20250417181347M0BOY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0BOY-DP!5200.64N/000-46.62rRNG0034 IPSC2-DVSPh-F MMDVM 438.8750@-8.0 MHz
20250417184603M0BOY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0BOY-DP!5200.64N/000-46.62rRNG0034 IPSC2-DVSPh-F MMDVM 438.8750@-8.0 MHz
20250417202254M0BOY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0BOY-DP!5200.64N/000-46.62rRNG0034 IPSC2-DVSPh-F MMDVM 438.8750@-8.0 MHz