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
20260115052859	OE7AOT-2>APRS,qAO,OE7XUT-12:!4728.34N/01237.36E_000/00 g...t033r000p...P...h71b09259 Lux:0 LoRa WX Hochfilzen
20260115054131	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t032r000p...P...h71b09258 Lux:0 LoRa WX Hochfilzen
20260115073305	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t034r000p...P...h72b09266 Lux:670 LoRa WX Hochfilzen
20260115082750	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t038r000p...P...h72b09269 Lux:1741 LoRa WX Hochfilzen
20260115085148	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t040r000p...P...h71b09272 Lux:2601 LoRa WX Hochfilzen
20260115090421	OE7AOT-2>APRS,qAO,OE7XUT-12:!4728.34N/01237.36E_315/00 g...t041r000p...P...h71b09273 Lux:2839 LoRa WX Hochfilzen