APRS Packet Errors for DL0MZ-15 (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
20260209103706	DL0MZ-15>APOTW1,TCPIP*,qAC,T2NUERNBG:!4959.82NL00816.69E&PHG0000Lora iGate 0.6
20260209110706	DL0MZ-15>APOTW1,TCPIP*,qAC,T2NUERNBG:!4959.82NL00816.69E&PHG0000Lora iGate 0.6
20260209113711	DL0MZ-15>APOTW1,TCPIP*,qAC,T2NUERNBG:!4959.82NL00816.69E&PHG0000Lora iGate 0.6
20260209120716	DL0MZ-15>APOTW1,TCPIP*,qAC,T2NUERNBG:!4959.82NL00816.69E&PHG0000Lora iGate 0.6
20260209123716	DL0MZ-15>APOTW1,TCPIP*,qAC,T2NUERNBG:!4959.82NL00816.69E&PHG0000Lora iGate 0.6
20260209125102	DL0MZ-15>APOTW1,TCPIP*,qAC,T2NUERNBG:!4959.82NL00816.69E&PHG0000Lora iGate 0.6
20260209132104	DL0MZ-15>APOTW1,TCPIP*,qAC,T2NUERNBG:!4959.82NL00816.69E&PHG0000Lora iGate 0.6
20260209135105	DL0MZ-15>APOTW1,TCPIP*,qAC,T2NUERNBG:!4959.82NL00816.69E&PHG0000Lora iGate 0.6
20260209142105	DL0MZ-15>APOTW1,TCPIP*,qAC,T2NUERNBG:!4959.82NL00816.69E&PHG0000Lora iGate 0.6
20260209145110	DL0MZ-15>APOTW1,TCPIP*,qAC,T2NUERNBG:!4959.82NL00816.69E&PHG0000Lora iGate 0.6
20260209152115	DL0MZ-15>APOTW1,TCPIP*,qAC,T2NUERNBG:!4959.82NL00816.69E&PHG0000Lora iGate 0.6
20260209155120	DL0MZ-15>APOTW1,TCPIP*,qAC,T2NUERNBG:!4959.82NL00816.69E&PHG0000Lora iGate 0.6
20260209162125	DL0MZ-15>APOTW1,TCPIP*,qAC,T2NUERNBG:!4959.82NL00816.69E&PHG0000Lora iGate 0.6