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
20250715163459	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_180/00 g...t071r000p...P...h74b09290 Lux:6359 LoRa WX Hochfilzen
20250715164948	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_045/00 g...t067r000p...P...h75b09292 Lux:871 LoRa WX Hochfilzen
20250715165530	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t066r000p...P...h75b09294 Lux:1097 LoRa WX Hochfilzen
20250715182318	OE7AOT-2>APRS,qAO,OE7XUT-12:!4728.34N/01237.36E_000/00 g...t059r000p...P...h78b09300 Lux:132 LoRa WX Hochfilzen
20250715191906	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_270/00 g...t058r000p...P...h78b09301 Lux:2 LoRa WX Hochfilzen