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
20250816115726HB9GZE-1>APOTW1,TCPIP*,qAC,T2CZECH:!47.519803NL7.555348 E&PHG0000Lora iGate
20250816122726HB9GZE-1>APOTW1,TCPIP*,qAC,T2CZECH:!47.519803NL7.555348 E&PHG0000Lora iGate
20250816125726HB9GZE-1>APOTW1,TCPIP*,qAC,T2CZECH:!47.519803NL7.555348 E&PHG0000Lora iGate
20250816132726HB9GZE-1>APOTW1,TCPIP*,qAC,T2CZECH:!47.519803NL7.555348 E&PHG0000Lora iGate
20250816135731HB9GZE-1>APOTW1,TCPIP*,qAC,T2CZECH:!47.519803NL7.555348 E&PHG0000Lora iGate
20250816140109HB9GZE-1>APOTW1,TCPIP*,qAC,T2FRANCE:!47.519803NL7.555348 E&PHG0000Lora iGate
20250816143112HB9GZE-1>APOTW1,TCPIP*,qAC,T2FRANCE:!47.519803NL7.555348 E&PHG0000Lora iGate
20250816150112HB9GZE-1>APOTW1,TCPIP*,qAC,T2FRANCE:!47.519803NL7.555348 E&PHG0000Lora iGate
20250816153112HB9GZE-1>APOTW1,TCPIP*,qAC,T2FRANCE:!47.519803NL7.555348 E&PHG0000Lora iGate
20250816160117HB9GZE-1>APOTW1,TCPIP*,qAC,T2FRANCE:!47.519803NL7.555348 E&PHG0000Lora iGate
20250816163122HB9GZE-1>APOTW1,TCPIP*,qAC,T2FRANCE:!47.519803NL7.555348 E&PHG0000Lora iGate
20250816170122HB9GZE-1>APOTW1,TCPIP*,qAC,T2FRANCE:!47.519803NL7.555348 E&PHG0000Lora iGate
20250816173122HB9GZE-1>APOTW1,TCPIP*,qAC,T2FRANCE:!47.519803NL7.555348 E&PHG0000Lora iGate