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
20260213045815OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_000/00 g...t037r000p...P...h74b09054 Lux:0 LoRa WX Hochfilzen
20260213051302OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_225/00 g...t037r000p...P...h73b09053 Lux:0 LoRa WX Hochfilzen
20260213071822OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_270/00 g...t038r000p...P...h73b09060 Lux:1743 LoRa WX Hochfilzen
20260213075816OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_315/00 g...t041r000p...P...h72b09063 Lux:3374 LoRa WX Hochfilzen
20260213075925OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_000/00 g...t041r000p...P...h72b09063 Lux:3411 LoRa WX Hochfilzen