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
20251224063744OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t028r000p...P...h74b09226 Lux:0 LoRa WX Hochfilzen
20251224065557OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t028r000p...P...h74b09227 Lux:10 LoRa WX Hochfilzen
20251224070246OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t028r000p...P...h74b09228 Lux:21 LoRa WX Hochfilzen
20251224071409OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t028r000p...P...h74b09229 Lux:45 LoRa WX Hochfilzen
20251224084520OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_045/00 g...t029r000p...P...h74b09230 Lux:390 LoRa WX Hochfilzen
20251224085901OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_180/00 g...t029r000p...P...h74b09231 Lux:385 LoRa WX Hochfilzen
20251224090443OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_270/00 g...t030r000p...P...h74b09231 Lux:477 LoRa WX Hochfilzen
20251224091242OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t030r000p...P...h74b09232 Lux:448 LoRa WX Hochfilzen
20251224095129OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_045/00 g...t030r000p...P...h74b09230 Lux:908 LoRa WX Hochfilzen
20251224102908OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t030r000p...P...h73b09227 Lux:787 LoRa WX Hochfilzen