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
20251009145211	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t057r000p...P...h77b09323 Lux:1839 LoRa WX Hochfilzen
20251009145319	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_315/00 g...t057r000p...P...h77b09323 Lux:2024 LoRa WX Hochfilzen
20251009151351	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_180/00 g...t057r000p...P...h77b09324 Lux:1292 LoRa WX Hochfilzen
20251009153423	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_225/00 g...t056r000p...P...h77b09327 Lux:846 LoRa WX Hochfilzen
20251009164829	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_270/00 g...t053r000p...P...h79b09332 Lux:5 LoRa WX Hochfilzen
20251009172021	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_225/00 g...t053r000p...P...h79b09336 Lux:0 LoRa WX Hochfilzen
20251009193654	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_090/00 g...t050r000p...P...h79b09350 Lux:0 LoRa WX Hochfilzen
20251009195615	OE7AOT-2>APRS,qAO,OE7AOT-10:!4728.34N/01237.36E_045/00 g...t050r000p...P...h79b09352 Lux:0 LoRa WX Hochfilzen