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
20260118045349OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t029r000p...P...h69b09271 Lux:0 LoRa WX Hochfilzen
20260118051743OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_180/00 g...t029r000p...P...h69b09270 Lux:0 LoRa WX Hochfilzen
20260118060747OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_045/00 g...t029r000p...P...h69b09273 Lux:0 LoRa WX Hochfilzen
20260118063033OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_315/00 g...t029r000p...P...h70b09272 Lux:9 LoRa WX Hochfilzen
20260118064047OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t029r000p...P...h70b09272 Lux:48 LoRa WX Hochfilzen
20260118073423OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t030r000p...P...h70b09275 Lux:822 LoRa WX Hochfilzen
20260118073531OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t030r000p...P...h70b09275 Lux:837 LoRa WX Hochfilzen
20260118081310OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t031r000p...P...h70b09276 Lux:1235 LoRa WX Hochfilzen
20260118083816OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t032r000p...P...h70b09276 Lux:1465 LoRa WX Hochfilzen
20260118084615OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t032r000p...P...h70b09276 Lux:1540 LoRa WX Hochfilzen