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
20260418170526	OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_315/00 g...t064r000p...P...h69b09278 Lux:1733 LoRa WX Hochfilzen
20260418174738	OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_270/00 g...t057r000p...P...h72b09280 Lux:444 LoRa WX Hochfilzen
20260418175754	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_270/00 g...t055r000p...P...h72b09280 Lux:202 LoRa WX Hochfilzen
20260418180228	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_270/00 g...t054r000p...P...h71b09281 Lux:137 LoRa WX Hochfilzen
20260418184543	OE7AOT-2>APRS,qAO,OE7XUT-12:!4728.34N/01237.36E_315/00 g...t050r000p...P...h71b09285 Lux:0 LoRa WX Hochfilzen
20260418185124	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t049r000p...P...h71b09286 Lux:0 LoRa WX Hochfilzen