APRS Packet Errors for LU2APR-1 (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
20260208130615	LU2APR-1>APE32A,WIDE2-2,qAR,LU1CJM-10:!3435.91SA05829.97W&PHG6330ESP32 IGate Message
20260208133614	LU2APR-1>APE32A,WIDE2-2,qAO,LU4AGC-10:!3435.91SA05829.97W&PHG6330ESP32 IGate Message
20260208140614	LU2APR-1>APE32A,WIDE2-2,qAO,LU4AGC-10:!3435.91SA05829.97W&PHG6330ESP32 IGate Message
20260208143614	LU2APR-1>APE32A,WIDE2-2,qAO,LU4AGC-10:!3435.91SA05829.97W&PHG6330ESP32 IGate Message
20260208150614	LU2APR-1>APE32A,WIDE2-2,qAR,LU9EHU-10:!3435.91SA05829.97W&PHG6330ESP32 IGate Message
20260208153614	LU2APR-1>APE32A,WIDE2-2,qAR,LU1CJM-10:!3435.91SA05829.97W&PHG6330ESP32 IGate Message
20260208160615	LU2APR-1>APE32A,WIDE2-2,qAR,LU9EHU-10:!3435.91SA05829.97W&PHG6330ESP32 IGate Message
20260208163615	LU2APR-1>APE32A,WIDE2-2,qAO,LU4AGC-10:!3435.91SA05829.97W&PHG6330ESP32 IGate Message
20260208170613	LU2APR-1>APE32A,WIDE2-2,qAR,LU9EHU-10:!3435.91SA05829.97W&PHG6330ESP32 IGate Message
20260208173616	LU2APR-1>APE32A,WIDE2-2,qAR,LU9EHU-10:!3435.91SA05829.97W&PHG6330ESP32 IGate Message
20260208180614	LU2APR-1>APE32A,WIDE2-2,qAO,LU4AGC-10:!3435.91SA05829.97W&PHG6330ESP32 IGate Message
20260208183614	LU2APR-1>APE32A,WIDE2-2,qAO,LU4AGC-10:!3435.91SA05829.97W&PHG6330ESP32 IGate Message