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
20260327185801	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_180/00 g...t028r000p...P...h71b09275 Lux:0 LoRa WX Hochfilzen
20260327190451	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_180/00 g...t028r000p...P...h71b09274 Lux:0 LoRa WX Hochfilzen
20260327190707	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_180/00 g...t028r000p...P...h71b09275 Lux:0 LoRa WX Hochfilzen
20260327190816	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_180/00 g...t028r000p...P...h71b09275 Lux:0 LoRa WX Hochfilzen
20260327202105	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_180/00 g...t028r000p...P...h72b09277 Lux:0 LoRa WX Hochfilzen
20260327220005	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_180/00 g...t028r000p...P...h72b09275 Lux:0 LoRa WX Hochfilzen
20260327220804	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_180/00 g...t028r000p...P...h72b09275 Lux:0 LoRa WX Hochfilzen