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
20250918181342	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t058r000p...P...h75b09362 Lux:0 LoRa WX Hochfilzen
20250918184642	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t056r000p...P...h75b09364 Lux:0 LoRa WX Hochfilzen
20250918190711	OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_315/00 g...t056r000p...P...h76b09366 Lux:0 LoRa WX Hochfilzen
20250918200257	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t055r000p...P...h76b09369 Lux:0 LoRa WX Hochfilzen
20250918213142	OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_000/00 g...t053r000p...P...h76b09375 Lux:0 LoRa WX Hochfilzen
20250918214521	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t053r000p...P...h76b09374 Lux:0 LoRa WX Hochfilzen
20250918221457	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t053r000p...P...h76b09374 Lux:0 LoRa WX Hochfilzen
20250918233909	OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_315/00 g...t053r000p...P...h77b09377 Lux:0 LoRa WX Hochfilzen
20250918235613	OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_315/00 g...t052r000p...P...h76b09377 Lux:0 LoRa WX Hochfilzen