APRS Packet Errors for M3YSV (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
20251107212723M3YSV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M3YSV-DP!5240.02N/000-10.28rRNG0034 IPSC2-DVSPh-F MMDVM 439.7125@-9.0 MHz
20251107215907M3YSV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M3YSV-DP!5240.02N/000-10.28rRNG0034 IPSC2-DVSPh-F MMDVM 439.7125@-9.0 MHz
20251107223048M3YSV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M3YSV-DP!5240.02N/000-10.28rRNG0034 IPSC2-DVSPh-F MMDVM 439.7125@-9.0 MHz
20251107230228M3YSV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M3YSV-DP!5240.02N/000-10.28rRNG0034 IPSC2-DVSPh-F MMDVM 439.7125@-9.0 MHz
20251107233405M3YSV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M3YSV-DP!5240.02N/000-10.28rRNG0034 IPSC2-DVSPh-F MMDVM 439.7125@-9.0 MHz
20251108000605M3YSV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M3YSV-DP!5240.02N/000-10.28rRNG0034 IPSC2-DVSPh-F MMDVM 439.7125@-9.0 MHz
20251108003752M3YSV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M3YSV-DP!5240.02N/000-10.28rRNG0034 IPSC2-DVSPh-F MMDVM 439.7125@-9.0 MHz
20251108010937M3YSV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M3YSV-DP!5240.02N/000-10.28rRNG0034 IPSC2-DVSPh-F MMDVM 439.7125@-9.0 MHz
20251108021317M3YSV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M3YSV-DP!5240.02N/000-10.28rRNG0034 IPSC2-DVSPh-F MMDVM 439.7125@-9.0 MHz