APRS Packet Errors for LU1TP-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
20260208144011	LU1TP-1>APBK22,WIDE1-1,WIDE2-2,qAR,LU4TDG-10:!2413.25S6504.05W#PHG3030Digipeater LU1TP CERRO ZAPLA
20260208152451	LU1TP-1>APBK22,WIDE1-1,WIDE2-2,qAR,LU4TDG-10:!2413.25S6504.05W#PHG3030Digipeater LU1TP CERRO ZAPLA
20260208155437	LU1TP-1>APBK22,WIDE1-1,WIDE2-2,qAR,LU4TDG-10:!2413.25S6504.05W#PHG3030Digipeater LU1TP CERRO ZAPLA
20260208173849	LU1TP-1>APBK22,WIDE1-1,WIDE2-2,qAR,LU4TDG-10:!2413.25S6504.05W#PHG3030Digipeater LU1TP CERRO ZAPLA
20260208180835	LU1TP-1>APBK22,WIDE1-1,WIDE2-2,qAR,LU4TDG-10:!2413.25S6504.05W#PHG3030Digipeater LU1TP CERRO ZAPLA
20260208183821	LU1TP-1>APBK22,WIDE1-1,WIDE2-2,qAR,LU4TDG-10:!2413.25S6504.05W#PHG3030Digipeater LU1TP CERRO ZAPLA
20260208192305	LU1TP-1>APBK22,WIDE1-1,WIDE2-2,qAR,LU4TDG-10:!2413.25S6504.05W#PHG3030Digipeater LU1TP CERRO ZAPLA
20260208195248	LU1TP-1>APBK22,WIDE1-1,WIDE2-2,qAR,LU4TDG-10:!2413.25S6504.05W#PHG3030Digipeater LU1TP CERRO ZAPLA
20260208195619	LU1TP-1>APBK22,WIDE1-1,WIDE2-2,qAR,LU4TDG-10:!2413.25S6504.05W#PHG3030Digipeater LU1TP CERRO ZAPLA