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
20260323012126OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t033r000p...P...h72b09215 Lux:0 LoRa WX Hochfilzen
20260323012451OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t033r000p...P...h72b09214 Lux:0 LoRa WX Hochfilzen
20260323013033OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t033r000p...P...h73b09214 Lux:0 LoRa WX Hochfilzen
20260323015318OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_270/00 g...t033r000p...P...h71b09215 Lux:0 LoRa WX Hochfilzen
20260323021131OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t032r000p...P...h71b09215 Lux:0 LoRa WX Hochfilzen
20260323024756OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t034r000p...P...h72b09216 Lux:0 LoRa WX Hochfilzen
20260323030716OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t033r000p...P...h71b09217 Lux:0 LoRa WX Hochfilzen
20260323045158OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t032r000p...P...h70b09223 Lux:10 LoRa WX Hochfilzen
20260323053842OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t029r000p...P...h68b09226 Lux:720 LoRa WX Hochfilzen
20260323055913OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t030r000p...P...h68b09227 Lux:1231 LoRa WX Hochfilzen