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
20260605020500	OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_270/00 g...t049r000p...P...h77b09227 Lux:0 LoRa WX Hochfilzen
20260605025504	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_090/00 g...t049r000p...P...h77b09231 Lux:1 LoRa WX Hochfilzen
20260605040906	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_090/00 g...t048r000p...P...h76b09241 Lux:325 LoRa WX Hochfilzen
20260605044644	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_180/00 g...t047r000p...P...h76b09245 Lux:542 LoRa WX Hochfilzen
20260605052856	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_225/00 g...t048r000p...P...h76b09253 Lux:1047 LoRa WX Hochfilzen
20260605070811	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t050r000p...P...h74b09261 Lux:2642 LoRa WX Hochfilzen