APRS Packet Errors for KD0SFY-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
20260209091352KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@091351hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260209092822KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@092821hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260209094252KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@094251hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260209095722KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@095721hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260209101152KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@101151hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260209102622KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@102621hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260209104052KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@104051hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260209105522KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@105521hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260209110952KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@110951hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260209112422KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@112421hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260209113852KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@113851hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260209115322KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@115321hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260209120752KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@120751hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260209122222KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@122222hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260209123652KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@123652hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260209125122KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@125122hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260209130552KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@130552hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260209132022KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@132022hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260209133452KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@133452hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260209134922KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@134922hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260209140352KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@140352hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260209141822KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@141822hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260209143252KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@143252hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260209144722KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@144722hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260209150152KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@150152hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate