APRS Packet Errors for OE3XFW-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
20260208134220OE3XFW-11>APOTW1,TCPIP*,qAC,T2GB:!4808.46NL01559.31E&PHG7360IGATE_LoRa Hochstrass 433.775
20260208141220OE3XFW-11>APOTW1,TCPIP*,qAC,T2GB:!4808.46NL01559.31E&PHG7360IGATE_LoRa Hochstrass 433.775
20260208144225OE3XFW-11>APOTW1,TCPIP*,qAC,T2GB:!4808.46NL01559.31E&PHG7360IGATE_LoRa Hochstrass 433.775
20260208151225OE3XFW-11>APOTW1,TCPIP*,qAC,T2GB:!4808.46NL01559.31E&PHG7360IGATE_LoRa Hochstrass 433.775
20260208154227OE3XFW-11>APOTW1,TCPIP*,qAC,T2GB:!4808.46NL01559.31E&PHG7360IGATE_LoRa Hochstrass 433.775
20260208161230OE3XFW-11>APOTW1,TCPIP*,qAC,T2GB:!4808.46NL01559.31E&PHG7360IGATE_LoRa Hochstrass 433.775
20260208164235OE3XFW-11>APOTW1,TCPIP*,qAC,T2GB:!4808.46NL01559.31E&PHG7360IGATE_LoRa Hochstrass 433.775
20260208171235OE3XFW-11>APOTW1,TCPIP*,qAC,T2GB:!4808.46NL01559.31E&PHG7360IGATE_LoRa Hochstrass 433.775
20260208174235OE3XFW-11>APOTW1,TCPIP*,qAC,T2GB:!4808.46NL01559.31E&PHG7360IGATE_LoRa Hochstrass 433.775
20260208181235OE3XFW-11>APOTW1,TCPIP*,qAC,T2GB:!4808.46NL01559.31E&PHG7360IGATE_LoRa Hochstrass 433.775
20260208184240OE3XFW-11>APOTW1,TCPIP*,qAC,T2GB:!4808.46NL01559.31E&PHG7360IGATE_LoRa Hochstrass 433.775
20260208191245OE3XFW-11>APOTW1,TCPIP*,qAC,T2GB:!4808.46NL01559.31E&PHG7360IGATE_LoRa Hochstrass 433.775