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
20260218233643	OE7AOT-2>APRS,qAO,OE7XUT-12:!4728.34N/01237.36E_315/00 g...t032r000p...P...h73b09134 Lux:0 LoRa WX Hochfilzen
20260219003445	OE7AOT-2>APRS,qAO,OE7XUT-12:!4728.34N/01237.36E_270/00 g...t032r000p...P...h73b09135 Lux:0 LoRa WX Hochfilzen
20260219003726	OE7AOT-2>APRS,qAO,OE7XUT-12:!4728.34N/01237.36E_315/00 g...t032r000p...P...h73b09135 Lux:0 LoRa WX Hochfilzen
20260219032310	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t030r000p...P...h72b09105 Lux:0 LoRa WX Hochfilzen
20260219032527	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t030r000p...P...h72b09105 Lux:0 LoRa WX Hochfilzen
20260219033108	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t030r000p...P...h72b09107 Lux:0 LoRa WX Hochfilzen
20260219034447	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t031r000p...P...h73b09103 Lux:0 LoRa WX Hochfilzen
20260219041856	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t030r000p...P...h72b09101 Lux:0 LoRa WX Hochfilzen