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
20251221074030	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_225/00 g...t033r000p...P...h73b09219 Lux:927 LoRa WX Hochfilzen
20251221075046	OE7AOT-2>APRS,qAO,OE7XUT-12:!4728.34N/01237.36E_315/00 g...t034r000p...P...h72b09219 Lux:1050 LoRa WX Hochfilzen
20251221080319	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t034r000p...P...h72b09219 Lux:1177 LoRa WX Hochfilzen
20251221080644	OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_180/00 g...t034r000p...P...h72b09219 Lux:1210 LoRa WX Hochfilzen
20251221081700	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t035r000p...P...h73b09219 Lux:1304 LoRa WX Hochfilzen
20251221082350	OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_270/00 g...t035r000p...P...h73b09219 Lux:1365 LoRa WX Hochfilzen
20251221083041	OE7AOT-2>APRS,qAO,OE7XUT-12:!4728.34N/01237.36E_315/00 g...t035r000p...P...h72b09219 Lux:1424 LoRa WX Hochfilzen
20251221085912	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_180/00 g...t035r000p...P...h71b09217 Lux:1654 LoRa WX Hochfilzen
20251221110007	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_090/00 g...t080r000p...P...h60b09199 Lux:38983 LoRa WX Hochfilzen