APRS Packet Errors for DK6OC-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
20250614153901DK6OC-1>APLRT1,WIDE1-1,qAO,DK6OC-10:=/4Z1dP68U_=VQ.../...g...t094h34b10196
20250614154903DK6OC-1>APLRT1,WIDE1-1,qAO,DK6OC-10:=/4Z1WP68a_=KQ.../...g...t094h35b10193QRV on C4FM: 26455|+!%U|
20250614155902DK6OC-1>APLRT1,WIDE1-1,qAO,DK6OC-10:=/4Z1]P68U_=gQ.../...g...t094h35b10196
20250614160903DK6OC-1>APLRT1,WIDE1-1,qAO,DK6OC-10:=/4Z1mP68N_
20250614165429DK6OC-1>APLRT1,WIDE1-1,qAO,DK6OC-10:=/4Z2.P68U_@NQ.../...g...t094h36b10234
20250614170429DK6OC-1>APLRT1,WIDE1-1,qAO,DK6OC-10:=/4Z1^P68P_
20250614171429DK6OC-1>APLRT1,WIDE1-1,qAO,DK6OC-10:=/4Z1]P68__=yQ.../...g...t094h36b10193
20250614175228DK6OC-1>APLRT1,WIDE1-1,qAO,DK6OC-10:=/4Z1eP68A_:WQ.../...g...t094h37b10165
20250614195945DK6OC-1>APLRT1,WIDE1-1,qAO,DK6OC-10:=/4Z0zP683_=lQ.../...g...t091h39b10206
20250614200946DK6OC-1>APLRT1,WIDE1-1,qAO,DK6OC-10:=/4Z1DP68S_
20250614201946DK6OC-1>APLRT1,WIDE1-1,qAO,DK6OC-10:=/4Z1XP68N_=@Q.../...g...t090h40b10204