APRS Packet Errors for LZ0DAD-DP (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
20260208144114LZ0DAD>APZDMR,QTH,TCPIP*,qAU,FOURTH:)LZ0DAD-DP!4249.31N/02741.78ErRNG0034 IPSC2-BULGARIA MMDVM 438.5000@-7.6 MHz
20260208151129LZ0DAD>APZDMR,QTH,TCPIP*,qAU,FOURTH:)LZ0DAD-DP!4249.31N/02741.78ErRNG0034 IPSC2-BULGARIA MMDVM 438.5000@-7.6 MHz
20260208154144LZ0DAD>APZDMR,QTH,TCPIP*,qAU,FOURTH:)LZ0DAD-DP!4249.31N/02741.78ErRNG0034 IPSC2-BULGARIA MMDVM 438.5000@-7.6 MHz
20260208161201LZ0DAD>APZDMR,QTH,TCPIP*,qAU,FOURTH:)LZ0DAD-DP!4249.31N/02741.78ErRNG0034 IPSC2-BULGARIA MMDVM 438.5000@-7.6 MHz
20260208164217LZ0DAD>APZDMR,QTH,TCPIP*,qAU,FOURTH:)LZ0DAD-DP!4249.31N/02741.78ErRNG0034 IPSC2-BULGARIA MMDVM 438.5000@-7.6 MHz
20260208174249LZ0DAD>APZDMR,QTH,TCPIP*,qAU,FOURTH:)LZ0DAD-DP!4249.31N/02741.78ErRNG0034 IPSC2-BULGARIA MMDVM 438.5000@-7.6 MHz
20260208181305LZ0DAD>APZDMR,QTH,TCPIP*,qAU,FOURTH:)LZ0DAD-DP!4249.31N/02741.78ErRNG0034 IPSC2-BULGARIA MMDVM 438.5000@-7.6 MHz
20260208184322LZ0DAD>APZDMR,QTH,TCPIP*,qAU,FOURTH:)LZ0DAD-DP!4249.31N/02741.78ErRNG0034 IPSC2-BULGARIA MMDVM 438.5000@-7.6 MHz
20260208191339LZ0DAD>APZDMR,QTH,TCPIP*,qAU,FOURTH:)LZ0DAD-DP!4249.31N/02741.78ErRNG0034 IPSC2-BULGARIA MMDVM 438.5000@-7.6 MHz