APRS Packet Errors for OE7BSH-8 (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
20250411195405	OE7BSH-8>APOTW1,TCPIP*,qAC,OE7XGR-10:!4728.12NI01160.3E&paperclip/IGate LoRa RX (no TX)
20250411202410	OE7BSH-8>APOTW1,TCPIP*,qAC,OE7XGR-10:!4728.12NI01160.3E&paperclip/IGate LoRa RX (no TX)
20250411205410	OE7BSH-8>APOTW1,TCPIP*,qAC,OE7XGR-10:!4728.12NI01160.3E&paperclip/IGate LoRa RX (no TX)
20250411212415	OE7BSH-8>APOTW1,TCPIP*,qAC,OE7XGR-10:!4728.12NI01160.3E&paperclip/IGate LoRa RX (no TX)
20250411215416	OE7BSH-8>APOTW1,TCPIP*,qAC,OE7XGR-10:!4728.12NI01160.3E&paperclip/IGate LoRa RX (no TX)
20250411222416	OE7BSH-8>APOTW1,TCPIP*,qAC,OE7XGR-10:!4728.12NI01160.3E&paperclip/IGate LoRa RX (no TX)
20250411225416	OE7BSH-8>APOTW1,TCPIP*,qAC,OE7XGR-10:!4728.12NI01160.3E&paperclip/IGate LoRa RX (no TX)
20250411232421	OE7BSH-8>APOTW1,TCPIP*,qAC,OE7XGR-10:!4728.12NI01160.3E&paperclip/IGate LoRa RX (no TX)
20250411235426	OE7BSH-8>APOTW1,TCPIP*,qAC,OE7XGR-10:!4728.12NI01160.3E&paperclip/IGate LoRa RX (no TX)
20250412002430	OE7BSH-8>APOTW1,TCPIP*,qAC,OE7XGR-10:!4728.12NI01160.3E&paperclip/IGate LoRa RX (no TX)
20250412005432	OE7BSH-8>APOTW1,TCPIP*,qAC,OE7XGR-10:!4728.12NI01160.3E&paperclip/IGate LoRa RX (no TX)
20250412012432	OE7BSH-8>APOTW1,TCPIP*,qAC,OE7XGR-10:!4728.12NI01160.3E&paperclip/IGate LoRa RX (no TX)