APRS Packet Errors for DB0TVH (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
20260208183002	DB0TVH>APRS,TCPIP*,qAS,DG1OBD:!5222.83N/00944.63ErBrandmeister DMR 439.900Mhz
20260208190001	DB0TVH>APRS,TCPIP*,qAS,DG1OBD:!5222.83N/00944.63ErBrandmeister DMR 439.900Mhz
20260208193001	DB0TVH>APRS,TCPIP*,qAS,DG1OBD:!5222.83N/00944.63ErBrandmeister DMR 439.900Mhz
20260208200002	DB0TVH>APRS,TCPIP*,qAS,DG1OBD:!5222.83N/00944.63ErBrandmeister DMR 439.900Mhz
20260208203001	DB0TVH>APRS,TCPIP*,qAS,DG1OBD:!5222.83N/00944.63ErBrandmeister DMR 439.900Mhz
20260208210001	DB0TVH>APRS,TCPIP*,qAS,DG1OBD:!5222.83N/00944.63ErBrandmeister DMR 439.900Mhz
20260208213002	DB0TVH>APRS,TCPIP*,qAS,DG1OBD:!5222.83N/00944.63ErBrandmeister DMR 439.900Mhz
20260208220002	DB0TVH>APRS,TCPIP*,qAS,DG1OBD:!5222.83N/00944.63ErBrandmeister DMR 439.900Mhz
20260208223001	DB0TVH>APRS,TCPIP*,qAS,DG1OBD:!5222.83N/00944.63ErBrandmeister DMR 439.900Mhz
20260208230001	DB0TVH>APRS,TCPIP*,qAS,DG1OBD:!5222.83N/00944.63ErBrandmeister DMR 439.900Mhz
20260208233002	DB0TVH>APRS,TCPIP*,qAS,DG1OBD:!5222.83N/00944.63ErBrandmeister DMR 439.900Mhz
20260209000001	DB0TVH>APRS,TCPIP*,qAS,DG1OBD:!5222.83N/00944.63ErBrandmeister DMR 439.900Mhz