APRS Packet Errors for DO4PPL (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
20260208141057DO4PPL>APBM1D,DMR*,qAS,BM2002-10:=5118.26N/01223.14E[225/009Daniel
20260208141329DO4PPL>APBM1D,DMR*,qAS,BM2002-10:=5118.24N/01223.10E[067/019Daniel
20260208141849DO4PPL>APBM1D,DMR*,qAS,BM2002-10:=5118.19N/01222.97E[247/001Daniel
20260208142338DO4PPL>APBM1D,DMR*,qAS,BM2002-10:=5118.18N/01222.93E[067/003Daniel
20260208142611DO4PPL>APBM1D,DMR*,qAS,BM2002-10:=5118.19N/01222.97E[067/006Daniel
20260208143116DO4PPL>APBM1D,DMR*,qAS,BM2002-10:=5118.18N/01222.89E[270/000Daniel
20260208143348DO4PPL>APBM1D,DMR*,qAS,BM2002-10:=5118.17N/01222.87E[067/001Daniel
20260208144357DO4PPL>APBM1D,DMR*,qAS,BM2002-10:=5118.19N/01222.94E[337/000Daniel