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
20260217154805	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_000/00 g...t034r000p...P...h73b09171 Lux:155 LoRa WX Hochfilzen
20260217174046	OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_045/00 g...t032r000p...P...h73b09176 Lux:0 LoRa WX Hochfilzen
20260217174302	OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_090/00 g...t032r000p...P...h73b09178 Lux:0 LoRa WX Hochfilzen
20260217175208	OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_045/00 g...t032r000p...P...h73b09187 Lux:0 LoRa WX Hochfilzen
20260217190025	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_045/00 g...t032r000p...P...h73b09190 Lux:0 LoRa WX Hochfilzen
20260217201748	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_045/00 g...t031r000p...P...h73b09200 Lux:0 LoRa WX Hochfilzen
20260217203817	OE7AOT-2>APRS,qAS,OE7XFJ-12:!4728.34N/01237.36E_000/00 g...t031r000p...P...h73b09205 Lux:0 LoRa WX Hochfilzen
20260217213511	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_135/00 g...t031r000p...P...h73b09208 Lux:0 LoRa WX Hochfilzen