APRS Packet Errors for OE7AOT-2 (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
20260203012200OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_180/00 g...t029r000p...P...h70b09101 Lux:0 LoRa WX Hochfilzen
20260203014012OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_270/00 g...t030r000p...P...h71b09102 Lux:0 LoRa WX Hochfilzen
20260203023450OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t032r000p...P...h70b09096 Lux:0 LoRa WX Hochfilzen
20260203032710OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t032r000p...P...h71b09091 Lux:0 LoRa WX Hochfilzen
20260203034158OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t033r000p...P...h72b09093 Lux:0 LoRa WX Hochfilzen
20260203040227OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t033r000p...P...h72b09094 Lux:0 LoRa WX Hochfilzen
20260203041025OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t033r000p...P...h72b09094 Lux:0 LoRa WX Hochfilzen
20260203054127OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_045/00 g...t033r000p...P...h72b09087 Lux:0 LoRa WX Hochfilzen