APRS Packet Errors for M6PZS (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
20260126034522M6PZS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M6PZS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20260126041711M6PZS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M6PZS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20260126044859M6PZS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M6PZS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20260126052047M6PZS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M6PZS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20260126055235M6PZS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M6PZS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20260126062423M6PZS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M6PZS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20260126072805M6PZS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M6PZS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20260126075956M6PZS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M6PZS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20260126083147M6PZS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M6PZS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20260126090340M6PZS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M6PZS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz