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
20260321060007OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_225/00 g...t032r000p...P...h69b09218 Lux:951 LoRa WX Hochfilzen
20260321062039OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_180/00 g...t032r000p...P...h69b09219 Lux:1285 LoRa WX Hochfilzen
20260321080210OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_090/00 g...t051r000p...P...h68b09214 Lux:6574 LoRa WX Hochfilzen
20260321105533OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t062r000p...P...h65b09210 Lux:14972 LoRa WX Hochfilzen
20260321110657OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_045/00 g...t0662°88ð...P...h65b09208 Lux:18935 LoRa WX ȇ)H aoIe]
20260321110658OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_045/00 g...t066r000p...P...h65b09208 Lux:18935 LoRa WX Hochfilzen