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
20260701181334OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_090/00 g...t058r000p...P...h78b09316 Lux:279 LoRa WX Hochfilzen
20260701181808OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t057r000p...P...h78b09316 Lux:249 LoRa WX Hochfilzen
20260701190449OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_090/00 g...t057r007p...P...h78b09321 Lux:9 LoRa WX Hochfilzen
20260701193749OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_135/00 g...t056r010p...P...h79b09326 Lux:0 LoRa WX Hochfilzen
20260701194223OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_180/00 g...t056r010p...P...h78b09326 Lux:0 LoRa WX Hochfilzen
20260701195928OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t056r000p...P...h79b09327 Lux:0 LoRa WX Hochfilzen
20260701220329OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t055r000p...P...h79b09324 Lux:0 LoRa WX Hochfilzen
20260701220437OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t055r000p...P...h79b09324 Lux:0 LoRa WX Hochfilzen
20260701225441OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_090/00 g...t055r000p...P...h79b09326 Lux:0 LoRa WX Hochfilzen
20260701231145OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_045/00 g...t055r000p...P...h79b09325 Lux:0 LoRa WX Hochfilzen