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
20260716233534	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_270/00 g...t062r000p...P...h77b09295 Lux:0 LoRa WX Hochfilzen
20260716234332	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t061r000p...P...h76b09294 Lux:0 LoRa WX Hochfilzen
20260716235711	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t061r000p...P...h76b09294 Lux:0 LoRa WX Hochfilzen
20260716235820	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_270/00 g...t061r000p...P...h77b09294 Lux:0 LoRa WX Hochfilzen
20260717000037	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t061r000p...P...h77b09294 Lux:0 LoRa WX Hochfilzen
20260717003809	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t061r000p...P...h77b09298 Lux:0 LoRa WX Hochfilzen
20260717004824	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t062r000p...P...h77b09295 Lux:0 LoRa WX Hochfilzen
20260717021601	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_225/00 g...t062r000p...P...h77b09293 Lux:0 LoRa WX Hochfilzen
20260717030822	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_270/00 g...t060r000p...P...h77b09287 Lux:5 LoRa WX Hochfilzen