APRS Packet Errors for DO2DAP-12 (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
20250418060946DO2DAP-12>APRS,qAO,DG2MEL-10:!4752.17N/01239.07E_.../...s000tnanhnanbnan0anan WX-Traunstein
20250418063951DO2DAP-12>APRS,qAO,DG2MEL-10:!4752.17N/01239.07E_.../...s000tnanhnanbnan0anan WX-Traunstein
20250418070957DO2DAP-12>APRS,qAO,DO2DAP-3:!4752.17N/01239.07E_.../...s000tnanhnanbnan0anan WX-Traunstein
20250418074002DO2DAP-12>APRS,qAO,DB0AAT-10:!4752.17N/01239.07E_.../...s000tnanhnanbnan0anan WX-Traunstein
20250418081008DO2DAP-12>APRS,qAO,DB0AAT-10:!4752.17N/01239.07E_.../...s000tnanhnanbnan0anan WX-Traunstein
20250418084013DO2DAP-12>APRS,qAO,DB0AAT-10:!4752.17N/01239.07E_.../...s000tnanhnanbnan0anan WX-Traunstein
20250418091019DO2DAP-12>APRS,qAO,DB0AAT-10:!4752.17N/01239.07E_.../...s000tnanhnanbnan0anan WX-Traunstein
20250418094025DO2DAP-12>APRS,qAO,DB0AAT-10:!4752.17N/01239.07E_.../...s000tnanhnanbnan0anan WX-Traunstein
20250418101030DO2DAP-12>APRS,qAO,DB0AAT-10:!4752.17N/01239.07E_.../...s000tnanhnanbnan0anan WX-Traunstein
20250418104036DO2DAP-12>APRS,qAO,DB0AAT-10:!4752.17N/01239.07E_.../...s000tnanhnanbnan0anan WX-Traunstein
20250418111041DO2DAP-12>APRS,qAO,DB0AAT-10:!4752.17N/01239.07E_.../...s000tnanhnanbnan0anan WX-Traunstein