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
20260626031755OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t060r000p...P...h75b09313 Lux:214 LoRa WX Hochfilzen
20260626032919OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t060r000p...P...h75b09314 Lux:414 LoRa WX Hochfilzen
20260626033935OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t060r000p...P...h74b09316 Lux:611 LoRa WX Hochfilzen
20260626044328OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t061r001p...P...h75b09316 Lux:1348 LoRa WX Hochfilzen
20260626051307OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t062r005p...P...h75b09318 Lux:1522 LoRa WX Hochfilzen
20260626051850OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t062r008p...P...h74b09317 Lux:1546 LoRa WX Hochfilzen
20260626054829OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t071r002p...P...h75b09317 Lux:2119 LoRa WX Hochfilzen