APRS Packet Errors for RA3TLB-15 (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
20260209090920RA3TLB-15>APMI01,TCPIP*,qAC,T2CHILE:@090909z5619.35N/04402.20E`N.Novgorod WX3IN1 Digipeater I-Gate
20260209092420RA3TLB-15>APMI01,TCPIP*,qAC,T2CHILE:@090924z5619.35N/04402.20E`N.Novgorod WX3IN1 Digipeater I-Gate
20260209093920RA3TLB-15>APMI01,TCPIP*,qAC,T2CHILE:@090939z5619.35N/04402.20E`N.Novgorod WX3IN1 Digipeater I-Gate
20260209095420RA3TLB-15>APMI01,TCPIP*,qAC,T2CHILE:@090954z5619.35N/04402.20E`N.Novgorod WX3IN1 Digipeater I-Gate
20260209100920RA3TLB-15>APMI01,TCPIP*,qAC,T2CHILE:@091009z5619.35N/04402.20E`N.Novgorod WX3IN1 Digipeater I-Gate
20260209102420RA3TLB-15>APMI01,TCPIP*,qAC,T2CHILE:@091024z5619.35N/04402.20E`N.Novgorod WX3IN1 Digipeater I-Gate
20260209103919RA3TLB-15>APMI01,TCPIP*,qAC,T2CHILE:@091039z5619.35N/04402.20E`N.Novgorod WX3IN1 Digipeater I-Gate
20260209105419RA3TLB-15>APMI01,TCPIP*,qAC,T2CHILE:@091054z5619.35N/04402.20E`N.Novgorod WX3IN1 Digipeater I-Gate
20260209110919RA3TLB-15>APMI01,TCPIP*,qAC,T2CHILE:@091109z5619.35N/04402.20E`N.Novgorod WX3IN1 Digipeater I-Gate
20260209112419RA3TLB-15>APMI01,TCPIP*,qAC,T2CHILE:@091124z5619.35N/04402.20E`N.Novgorod WX3IN1 Digipeater I-Gate
20260209113919RA3TLB-15>APMI01,TCPIP*,qAC,T2CHILE:@091139z5619.35N/04402.20E`N.Novgorod WX3IN1 Digipeater I-Gate
20260209115419RA3TLB-15>APMI01,TCPIP*,qAC,T2CHILE:@091154z5619.35N/04402.20E`N.Novgorod WX3IN1 Digipeater I-Gate
20260209120919RA3TLB-15>APMI01,TCPIP*,qAC,T2CHILE:@091209z5619.35N/04402.20E`N.Novgorod WX3IN1 Digipeater I-Gate
20260209122419RA3TLB-15>APMI01,TCPIP*,qAC,T2CHILE:@091224z5619.35N/04402.20E`N.Novgorod WX3IN1 Digipeater I-Gate
20260209123919RA3TLB-15>APMI01,TCPIP*,qAC,T2CHILE:@091239z5619.35N/04402.20E`N.Novgorod WX3IN1 Digipeater I-Gate
20260209125419RA3TLB-15>APMI01,TCPIP*,qAC,T2CHILE:@091254z5619.35N/04402.20E`N.Novgorod WX3IN1 Digipeater I-Gate
20260209130919RA3TLB-15>APMI01,TCPIP*,qAC,T2CHILE:@091309z5619.35N/04402.20E`N.Novgorod WX3IN1 Digipeater I-Gate
20260209132419RA3TLB-15>APMI01,TCPIP*,qAC,T2CHILE:@091324z5619.35N/04402.20E`N.Novgorod WX3IN1 Digipeater I-Gate
20260209133919RA3TLB-15>APMI01,TCPIP*,qAC,T2CHILE:@091339z5619.35N/04402.20E`N.Novgorod WX3IN1 Digipeater I-Gate
20260209135419RA3TLB-15>APMI01,TCPIP*,qAC,T2CHILE:@091354z5619.35N/04402.20E`N.Novgorod WX3IN1 Digipeater I-Gate
20260209140919RA3TLB-15>APMI01,TCPIP*,qAC,T2CHILE:@091409z5619.35N/04402.20E`N.Novgorod WX3IN1 Digipeater I-Gate
20260209142419RA3TLB-15>APMI01,TCPIP*,qAC,T2CHILE:@091424z5619.35N/04402.20E`N.Novgorod WX3IN1 Digipeater I-Gate
20260209143919RA3TLB-15>APMI01,TCPIP*,qAC,T2CHILE:@091439z5619.35N/04402.20E`N.Novgorod WX3IN1 Digipeater I-Gate
20260209145419RA3TLB-15>APMI01,TCPIP*,qAC,T2CHILE:@091454z5619.35N/04402.20E`N.Novgorod WX3IN1 Digipeater I-Gate