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
20260118120917OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_225/00 g...t097r000p...P...h38b09255 Lux:47601 LoRa WX Hochfilzen
20260118144642OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t083r000p...P...h40b09257 Lux:30911 LoRa WX Hochfilzen
20260118144750OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_270/00 g...t083r000p...P...h41b09257 Lux:29030 LoRa WX Hochfilzen
20260118152055OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_270/00 g...t058r000p...P...h54b09260 Lux:1695 LoRa WX Hochfilzen
20260118155834OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_315/00 g...t040r000p...P...h66b09265 Lux:163 LoRa WX Hochfilzen
20260118165853OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_315/00 g...t035r000p...P...h68b09271 Lux:0 LoRa WX Hochfilzen