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
20251112133015	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_180/00 g...t102r000p...P...h44b09261 Lux:42358 LoRa WX Hochfilzen
20251112140320	OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_135/00 g...t102r000p...P...h45b09259 Lux:32226 LoRa WX Hochfilzen
20251112143043	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_135/00 g...t102r000p...P...h43b09259 Lux:28106 LoRa WX Hochfilzen
20251112144641	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_180/00 g...t084r000p...P...h53b09262 Lux:8646 LoRa WX Hochfilzen
20251112144858	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_225/00 g...t081r000p...P...h54b09262 Lux:6983 LoRa WX Hochfilzen
20251112153544	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t052r000p...P...h71b09268 Lux:224 LoRa WX Hochfilzen
20251112161859	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_135/00 g...t047r000p...P...h73b09270 Lux:0 LoRa WX Hochfilzen
20251112171120	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_270/00 g...t043r000p...P...h74b09272 Lux:0 LoRa WX Hochfilzen