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
20260517030444	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_270/00 g...t038r000p...P...h75b09236 Lux:1 LoRa WX Hochfilzen
20260517031715	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t038r000p...P...h75b09237 Lux:12 LoRa WX Hochfilzen
20260517034652	OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_000/00 g...t039r000p...P...h75b09239 Lux:197 LoRa WX Hochfilzen
20260517040250	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t039r000p...P...h75b09239 Lux:677 LoRa WX Hochfilzen
20260517045518	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t037r000p...P...h73b09241 Lux:1542 LoRa WX Hochfilzen
20260517045735	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t037r000p...P...h73b09242 Lux:1567 LoRa WX Hochfilzen
20260517060019	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t051r000p...P...h74b09242 Lux:2988 LoRa WX Hochfilzen
20260517065613	OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_315/00 g...t059r000p...P...h66b09243 Lux:4472 LoRa WX Hochfilzen