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
20260513124431OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_090/`65g...t116r000p...P...h34b09148 Lux:54612 LoRa WX HochfilzenÀ
20260513164147OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_315/00 g...t076r000p...P...h51b09136 Lux:4039 LoRa WX Hochfilzen
20260513172725OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_270/00 g...t052r000p...P...h68b09143 Lux:1970 LoRa WX Hochfilzen
20260513175013OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_270/00 g...t050r000p...P...h71b09146 Lux:766 LoRa WX Hochfilzen
20260513175704OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t049r000p...P...h71b09145 Lux:688 LoRa WX Hochfilzen