APRS Packet Errors for DL4AAS-11 (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
20260209120114	DL4AAS-11>APOTW1,TCPIP*,qAC,HAMCLOUD1:!4929.42NI00949.20E&PHG01000/iGate lora-aprs.at
20260209123119	DL4AAS-11>APOTW1,TCPIP*,qAC,HAMCLOUD1:!4929.42NI00949.20E&PHG01000/iGate lora-aprs.at
20260209130124	DL4AAS-11>APOTW1,TCPIP*,qAC,HAMCLOUD1:!4929.42NI00949.20E&PHG01000/iGate lora-aprs.at
20260209133124	DL4AAS-11>APOTW1,TCPIP*,qAC,HAMCLOUD1:!4929.42NI00949.20E&PHG01000/iGate lora-aprs.at
20260209140129	DL4AAS-11>APOTW1,TCPIP*,qAC,HAMCLOUD1:!4929.42NI00949.20E&PHG01000/iGate lora-aprs.at
20260209143134	DL4AAS-11>APOTW1,TCPIP*,qAC,HAMCLOUD1:!4929.42NI00949.20E&PHG01000/iGate lora-aprs.at
20260209150134	DL4AAS-11>APOTW1,TCPIP*,qAC,HAMCLOUD1:!4929.42NI00949.20E&PHG01000/iGate lora-aprs.at
20260209153139	DL4AAS-11>APOTW1,TCPIP*,qAC,HAMCLOUD1:!4929.42NI00949.20E&PHG01000/iGate lora-aprs.at
20260209160144	DL4AAS-11>APOTW1,TCPIP*,qAC,HAMCLOUD1:!4929.42NI00949.20E&PHG01000/iGate lora-aprs.at
20260209163144	DL4AAS-11>APOTW1,TCPIP*,qAC,HAMCLOUD1:!4929.42NI00949.20E&PHG01000/iGate lora-aprs.at
20260209170149	DL4AAS-11>APOTW1,TCPIP*,qAC,HAMCLOUD1:!4929.42NI00949.20E&PHG01000/iGate lora-aprs.at
20260209173154	DL4AAS-11>APOTW1,TCPIP*,qAC,HAMCLOUD1:!4929.42NI00949.20E&PHG01000/iGate lora-aprs.at