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
20251017192244	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_135/00 g...t044r000p...P...h77b09306 Lux:0 LoRa WX Hochfilzen
20251017200342	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t044r000p...P...h77b09309 Lux:0 LoRa WX Hochfilzen
20251017213119	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t043r000p...P...h77b09311 Lux:0 LoRa WX Hochfilzen
20251017221109	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t042r000p...P...h77b09311 Lux:0 LoRa WX Hochfilzen
20251017222340	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_180/00 g...t042r000p...P...h77b09311 Lux:0 LoRa WX Hochfilzen
20251017223611	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t042r000p...P...h77b09310 Lux:0 LoRa WX Hochfilzen
20251017224625	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t042r000p...P...h77b09311 Lux:0 LoRa WX Hochfilzen
20251017234900	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t042r000p...P...h77b09311 Lux:0 LoRa WX Hochfilzen
20251018003756	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t042r000p...P...h77b09310 Lux:0 LoRa WX Hochfilzen
20251018010042	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t042r000p...P...h77b09309 Lux:0 LoRa WX Hochfilzen