APRS Packet Errors for IRLP_2018 (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
20260209104011	VE2REH-3>APN391,qAR,VA2BBW-2:;IRLP_2018*111111z4548.00NI07509.49W0147.390Mhz T146.2 VE2REH
20260209111013	VE2REH-3>APN391,qAR,VE3JCT:;IRLP_2018*111111z4548.00NI07509.49W0147.390Mhz T146.2 VE2REH
20260209114011	VE2REH-3>APN391,qAR,VE3JCT:;IRLP_2018*111111z4548.00NI07509.49W0147.390Mhz T146.2 VE2REH
20260209121011	VE2REH-3>APN391,qAO,VE2PCQ-3:;IRLP_2018*111111z4548.00NI07509.49W0147.390Mhz T146.2 VE2REH
20260209124013	VE2REH-3>APN391,qAR,VE3JCT:;IRLP_2018*111111z4548.00NI07509.49W0147.390Mhz T146.2 VE2REH
20260209131011	VE2REH-3>APN391,qAR,VE3JCT:;IRLP_2018*111111z4548.00NI07509.49W0147.390Mhz T146.2 VE2REH
20260209134011	VE2REH-3>APN391,qAR,VE3JCT:;IRLP_2018*111111z4548.00NI07509.49W0147.390Mhz T146.2 VE2REH
20260209141011	VE2REH-3>APN391,qAR,VE3JCT:;IRLP_2018*111111z4548.00NI07509.49W0147.390Mhz T146.2 VE2REH
20260209144011	VE2REH-3>APN391,qAR,VE3JCT:;IRLP_2018*111111z4548.00NI07509.49W0147.390Mhz T146.2 VE2REH
20260209151011	VE2REH-3>APN391,qAR,VE3JCT:;IRLP_2018*111111z4548.00NI07509.49W0147.390Mhz T146.2 VE2REH
20260209154011	VE2REH-3>APN391,qAR,VE3JCT:;IRLP_2018*111111z4548.00NI07509.49W0147.390Mhz T146.2 VE2REH
20260209161011	VE2REH-3>APN391,qAR,VE3JCT:;IRLP_2018*111111z4548.00NI07509.49W0147.390Mhz T146.2 VE2REH