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
20250418062327OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_135/00 g...t045r000p...P...h74b09207 Lux:2897 LoRa WX Hochfilzen
20250418073844OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t046r000p...P...h72b09212 Lux:3531 LoRa WX Hochfilzen
20250418075916OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_090/00 g...t047r000p...P...h72b09214 Lux:4032 LoRa WX Hochfilzen
20250418080133OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t047r000p...P...h72b09214 Lux:5014 LoRa WX Hochfilzen
20250418081514OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_135/00 g...t047r000p...P...h72b09215 Lux:4848 LoRa WX Hochfilzen
20250418081948OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_180/00 g...t048r000p...P...h72b09216 Lux:5629 LoRa WX Hochfilzen
20250418110620OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t052r000p...P...h68b09218 Lux:7310 LoRa WX Hochfilzen
20250418114250OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t055r000p...P...h67b09217 Lux:7085 LoRa WX Hochfilzen
20250418115306OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_270/00 g...t054r000p...P...h68b09217 Lux:7508 LoRa WX Hochfilzen