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
20260626203916	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t068r000p...P...h73b09322 Lux:0 LoRa WX Hochfilzen
20260626204457	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t067r000p...P...h73b09323 Lux:0 LoRa WX Hochfilzen
20260626213245	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t065r000p...P...h74b09323 Lux:0 LoRa WX Hochfilzen
20260626215639	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t065r000p...P...hnanb09324 Lux:0 LoRa WX Hochfilzen
20260626220545	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t065r000p...P...h74b09324 Lux:0 LoRa WX Hochfilzen
20260626222506	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t064r000p...P...h75b09325 Lux:0 LoRa WX Hochfilzen
20260627000839	OE7AOT-2>APRS,qAO,OE7XUT-12:!4728.34N/01237.36E_225/00 g...t064r000p...P...h75b09323 Lux:0 LoRa WX Hochfilzen
20260627001528	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t064r000p...P...h75b09323 Lux:0 LoRa WX Hochfilzen