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
20260223042429	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_090/00 g...t041r000p...P...h76b09279 Lux:0 LoRa WX Hochfilzen
20260223052015	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_270/00 g...t040r000p...P...h75b09282 Lux:0 LoRa WX Hochfilzen
20260223074500	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_090/00 g...t047r000p...P...h73b09281 Lux:4482 LoRa WX Hochfilzen
20260223080857	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_270/00 g...t051r000p...P...h72b09278 Lux:6354 LoRa WX Hochfilzen
20260223081005	OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_045/00 g...t051r000p...P...h72b09278 Lux:6170 LoRa WX Hochfilzen