APRS Packet Errors for OE5PON-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
20260208171533OE5PON-11>APOTW1,TCPIP*,qAC,OE5XOL:!4822.50NL01426.10E&PHG0000Lora iGate Alberndorf
20260208174533OE5PON-11>APOTW1,TCPIP*,qAC,OE5XOL:!4822.50NL01426.10E&PHG0000Lora iGate Alberndorf
20260208181538OE5PON-11>APOTW1,TCPIP*,qAC,OE5XOL:!4822.50NL01426.10E&PHG0000Lora iGate Alberndorf
20260208184538OE5PON-11>APOTW1,TCPIP*,qAC,OE5XOL:!4822.50NL01426.10E&PHG0000Lora iGate Alberndorf
20260208191538OE5PON-11>APOTW1,TCPIP*,qAC,OE5XOL:!4822.50NL01426.10E&PHG0000Lora iGate Alberndorf
20260208194538OE5PON-11>APOTW1,TCPIP*,qAC,OE5XOL:!4822.50NL01426.10E&PHG0000Lora iGate Alberndorf
20260208201543OE5PON-11>APOTW1,TCPIP*,qAC,OE5XOL:!4822.50NL01426.10E&PHG0000Lora iGate Alberndorf
20260208204543OE5PON-11>APOTW1,TCPIP*,qAC,OE5XOL:!4822.50NL01426.10E&PHG0000Lora iGate Alberndorf
20260208211543OE5PON-11>APOTW1,TCPIP*,qAC,OE5XOL:!4822.50NL01426.10E&PHG0000Lora iGate Alberndorf
20260208214548OE5PON-11>APOTW1,TCPIP*,qAC,OE5XOL:!4822.50NL01426.10E&PHG0000Lora iGate Alberndorf
20260208221548OE5PON-11>APOTW1,TCPIP*,qAC,OE5XOL:!4822.50NL01426.10E&PHG0000Lora iGate Alberndorf
20260208224553OE5PON-11>APOTW1,TCPIP*,qAC,OE5XOL:!4822.50NL01426.10E&PHG0000Lora iGate Alberndorf