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
20250913072505OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_090/00 g...t062r000p...P...h76b09305 Lux:3964 LoRa WX Hochfilzen
20250913072722OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_180/00 g...t062r000p...P...h76b09306 Lux:4655 LoRa WX Hochfilzen
20250913080027OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_135/00 g...t067r000p...P...h73b09304 Lux:7363 LoRa WX Hochfilzen
20250913104808OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_225/00 g...t096r000p...P...h59b09292 Lux:32764 LoRa WX Hochfilzen
20250913121124OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_045/00 g...t115r000p...P...h44b09284 Lux:48349 LoRa WX Hochfilzen
20250913125919OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_180/00 g...t123r000p...P...h41b09281 Lux:44641 LoRa WX Hochfilzen