APRS Packet Errors for DL4SDR-35 (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
20250701010508	DL4SDR-35>APLT00-1,WIDE1-1,qAO,DK4SDR-10:=M5L*ZPxZM P[Meshcom GW / DL
20250701013508	DL4SDR-35>APLT00-1,WIDE1-1,qAO,DK4SDR-10:=M5L*ZPxZM P[Meshcom GW / DL
20250701020508	DL4SDR-35>APLT00-1,WIDE1-1,qAO,DK4SDR-10:=M5L*ZPxZM P[Meshcom GW / DL
20250701023508	DL4SDR-35>APLT00-1,WIDE1-1,qAO,DK4SDR-10:=M5L*ZPxZM P[Meshcom GW / DL
20250701030508	DL4SDR-35>APLT00-1,WIDE1-1,qAO,DK4SDR-10:=M5L*ZPxZM P[Meshcom GW / DL
20250701033508	DL4SDR-35>APLT00-1,WIDE1-1,qAO,DK4SDR-10:=M5L*ZPxZM P[Meshcom GW / DL
20250701040508	DL4SDR-35>APLT00-1,WIDE1-1,qAO,DK4SDR-10:=M5L*ZPxZM P[Meshcom GW / DL
20250701043508	DL4SDR-35>APLT00-1,WIDE1-1,qAO,DK4SDR-10:=M5L*ZPxZM P[Meshcom GW / DL
20250701050508	DL4SDR-35>APLT00-1,WIDE1-1,qAO,DK4SDR-10:=M5L*ZPxZM P[Meshcom GW / DL
20250701053508	DL4SDR-35>APLT00-1,WIDE1-1,qAO,DK4SDR-10:=M5L*ZPxZM P[Meshcom GW / DL
20250701060508	DL4SDR-35>APLT00-1,WIDE1-1,qAO,DK4SDR-10:=M5L*ZPxZM P[Meshcom GW / DL
20250701063508	DL4SDR-35>APLT00-1,WIDE1-1,qAO,DK4SDR-10:=M5L*ZPxZM P[Meshcom GW / DL