APRS Packet Errors for IRLP-4717 (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
20260208143351K3BAY-2>APVR30,TCPIP*,qAC,T2BELGIUM:;IRLP-4717*081433z3909.29NI07629.91W0145.540MHz T107 20M IDLE
20260208143516K3BAY-2>APVR30,TCPIP*,qAC,T2CHILE:;IRLP-4717*081435z3909.29NI07629.91W0145.540MHz T107 20M IDLE
20260208145702K3BAY-2>APVR30,TCPIP*,qAC,T2UKRAINE:;IRLP-4717*081457z3909.29NI07629.91W0145.540MHz T107 20M IDLE
20260208155702K3BAY-2>APVR30,TCPIP*,qAC,T2PERTH:;IRLP-4717*081557z3909.29NI07629.91W0145.540MHz T107 20M IDLE
20260208165702K3BAY-2>APVR30,TCPIP*,qAC,T2ROMANIA:;IRLP-4717*081657z3909.29NI07629.91W0145.540MHz T107 20M IDLE
20260208175701K3BAY-2>APVR30,TCPIP*,qAC,T2PANAMA:;IRLP-4717*081757z3909.29NI07629.91W0145.540MHz T107 20M IDLE
20260208185702K3BAY-2>APVR30,TCPIP*,qAC,T2CSNGRAD:;IRLP-4717*081857z3909.29NI07629.91W0145.540MHz T107 20M IDLE
20260208192645K3BAY-2>APVR30,TCPIP*,qAC,T2PERTH:;IRLP-4717*081926z3909.29NC07629.91W0145.540MHz T107 20M C EL512541
20260208192950K3BAY-2>APVR30,TCPIP*,qAC,T2SYDNEY:;IRLP-4717*081929z3909.29NI07629.91W0145.540MHz T107 20M IDLE
20260208195702K3BAY-2>APVR30,TCPIP*,qAC,T2PERTH:;IRLP-4717*081957z3909.29NI07629.91W0145.540MHz T107 20M IDLE