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
20240302000603OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t039r000p...P...h77b09158 Lux:0 LoRa WX Hochfilzen
20240302002633OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t038r000p...P...h77b09158 Lux:0 LoRa WX Hochfilzen
20240302003430OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t038r000p...P...h78b09158 Lux:0 LoRa WX Hochfilzen
20240302004444OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t039r000p...P...h78b09159 Lux:0 LoRa WX Hochfilzen
20240302013233OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_180/00 g...t038r000p...P...h78b09158 Lux:0 LoRa WX Hochfilzen
20240302020640OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t038r000p...P...h77b09157 Lux:0 LoRa WX Hochfilzen
20240302021911OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t037r000p...P...h76b09156 Lux:0 LoRa WX Hochfilzen
20240302022344OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t037r000p...P...h76b09156 Lux:0 LoRa WX Hochfilzen
20240302022453OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_045/00 g...t037r000p...P...h76b09156 Lux:0 LoRa WX Hochfilzen
20240302022601OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t037r000p...P...h76b09156 Lux:0 LoRa WX Hochfilzen