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
20260605165104OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_000/00 g...t059r000p...P...h73b09256 Lux:1035 LoRa WX Hochfilzen
20260605170120OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_270/00 g...t059r000p...P...h74b09258 Lux:768 LoRa WX Hochfilzen
20260605172843OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t057r000p...P...h74b09261 Lux:527 LoRa WX Hochfilzen
20260605183018OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t057r000p...P...h75b09264 Lux:450 LoRa WX Hochfilzen
20260605185741OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t056r000p...P...h75b09265 Lux:115 LoRa WX Hochfilzen
20260605191445OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t055r000p...P...h75b09265 Lux:30 LoRa WX Hochfilzen
20260605202735OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t053r000p...P...h76b09270 Lux:0 LoRa WX Hochfilzen