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
20260208150620KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@150619hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260208152050KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@152049hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260208153520KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@153519hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260208154950KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@154949hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260208160420KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@160419hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260208161850KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@161849hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260208163320KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@163319hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260208164750KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@164749hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260208170220KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@170219hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260208171650KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@171649hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260208173120KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@173119hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260208174550KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@174549hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260208180020KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@180019hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260208181450KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@181450hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260208182920KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@182920hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260208184350KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@184350hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260208185820KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@185820hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260208191250KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@191250hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260208192720KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@192720hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260208194150KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@194150hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260208195620KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@195620hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260208201050KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@201050hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260208202520KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@202520hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260208203950KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@203950hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate
20260208205420KD0SFY-1>APJYC1,TCPIP*,qAC,T2PR:@205420hT:m1Z4!g&Q33PHG3330 Colorado Springs IGate