APRS Packet Errors for HB9GZE-1 (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
20250915141721HB9GZE-1>APOTW1,TCPIP*,qAC,T2UKRAINE:!47.519803NL7.555348 E&PHG0000Lora iGate
20250915151726HB9GZE-1>APOTW1,TCPIP*,qAC,T2UKRAINE:!47.519803NL7.555348 E&PHG0000Lora iGate
20250915153154HB9GZE-1>APOTW1,TCPIP*,qAC,T2SPAIN:!47.519803NL7.555348 E&PHG0000Lora iGate
20250915160158HB9GZE-1>APOTW1,TCPIP*,qAC,T2SPAIN:!47.519803NL7.555348 E&PHG0000Lora iGate
20250915163203HB9GZE-1>APOTW1,TCPIP*,qAC,T2SPAIN:!47.519803NL7.555348 E&PHG0000Lora iGate
20250915170208HB9GZE-1>APOTW1,TCPIP*,qAC,T2SPAIN:!47.519803NL7.555348 E&PHG0000Lora iGate
20250915173208HB9GZE-1>APOTW1,TCPIP*,qAC,T2SPAIN:!47.519803NL7.555348 E&PHG0000Lora iGate
20250915180208HB9GZE-1>APOTW1,TCPIP*,qAC,T2SPAIN:!47.519803NL7.555348 E&PHG0000Lora iGate
20250915183213HB9GZE-1>APOTW1,TCPIP*,qAC,T2SPAIN:!47.519803NL7.555348 E&PHG0000Lora iGate
20250915190213HB9GZE-1>APOTW1,TCPIP*,qAC,T2SPAIN:!47.519803NL7.555348 E&PHG0000Lora iGate
20250915193213HB9GZE-1>APOTW1,TCPIP*,qAC,T2SPAIN:!47.519803NL7.555348 E&PHG0000Lora iGate
20250915200213HB9GZE-1>APOTW1,TCPIP*,qAC,T2SPAIN:!47.519803NL7.555348 E&PHG0000Lora iGate