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
20251216070603OE7AOT-2>APRS,qAO,OE7XUT-12:!4728.34N/01237.36E_000/00 g...t040r000p...P...h73b09245 Lux:286 LoRa WX Hochfilzen
20251216072201OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_045/00 g...t040r000p...P...h72b09244 Lux:528 LoRa WX Hochfilzen
20251216073908OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_225/00 g...t040r000p...P...h72b09243 Lux:913 LoRa WX Hochfilzen
20251216074924OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_180/00 g...t041r000p...P...h72b09242 Lux:974 LoRa WX Hochfilzen
20251216085425OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_135/00 g...t047r000p...P...h72b09249 Lux:2938 LoRa WX Hochfilzen
20251216085641OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t048r000p...P...h72b09248 Lux:2993 LoRa WX Hochfilzen
20251216101307OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_135/00 g...t071r000p...P...h67b09243 Lux:19728 LoRa WX Hochfilzen
20251216101741OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t074r000p...P...h66b09242 Lux:18973 LoRa WX Hochfilzen
20251216115804OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_045/00 g...t080r000p...P...h52b09234 Lux:10225 LoRa WX Hochfilzen