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
20260218103257OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_000/00 g...t078r002p...P...h42b09198 Lux:35336 LoRa WX Hochfilzen
20260218103731OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t082r003p...P...h41b09197 Lux:39754 LoRa WX Hochfilzen
20260218123135OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_180/00 g...t064r000p...P...h56b09180 Lux:13383 LoRa WX Hochfilzen
20260218132038OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_135/00 g...t056r000p...P...h61b09176 Lux:16092 LoRa WX Hochfilzen
20260218141306OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_225/00 g...t049r000p...P...h66b09175 Lux:5209 LoRa WX Hochfilzen
20260218150426OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_090/00 g...t042r000p...P...h67b09173 Lux:2433 LoRa WX Hochfilzen
20260218154855OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_000/00 g...t038r000p...P...h70b09172 Lux:1045 LoRa WX Hochfilzen
20260218160128OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_180/00 g...t037r000p...P...h70b09171 Lux:854 LoRa WX Hochfilzen