APRS Packet Errors for IW2MUC-12 (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
20251013150201	IW2MUC-12>APLRT1,WIDE1-1,qAR,IW2MXO-10:!/7:sKQ($%_EVQ.../...g...t081r...p...P...h60b09930 Bat=3.96V (82%)
20251013151205	IW2MUC-12>APLRT1,WIDE1-1,qAR,IW2MUC-10:!/7:sIQ($#_ENQ.../...g...t079r...p...P...h61b09930 Bat=3.96V (81%)
20251013152209	IW2MUC-12>APLRT1,WIDE1-1,qAR,IW2MUC-10:!/7:sUQ($>_F@Q.../...g...t078r...p...P...h62b09930 Bat=3.95V (80%)
20251013153213	IW2MUC-12>APLRT1,WIDE1-1,qAO,IW2EJH-11:!/7:seQ($4_F:Q.../...g...t077r...p...P...h62b09930 Bat=3.94V (80%)
20251013154217	IW2MUC-12>APLRT1,WIDE1-1,qAR,IW2MUC-10:!/7:shQ($M_FNQ.../...g...t076r...p...P...h62b09930 Bat=3.93V (79%)
20251013155221	IW2MUC-12>APLRT1,WIDE1-1,qAR,IW2MXO-10:!/7:scQ($<_F0Q.../...g...t075r...p...P...h63b09940 Bat=3.93V (78%)
20251013160225	IW2MUC-12>APLRT1,WIDE1-1,qAR,IW2MUC-10:!/7:shQ($9_F2Q.../...g...t074r...p...P...h63b09930 Bat=3.92V (77%)
20251013170249	IW2MUC-12>APLRT1,WIDE1-1,qAR,IW2MXO-10:!/7:rAQ($#_F`Q.../...g...t069r...p...P...h63b09940 Bat=3.94V (72%)
20251013171253	IW2MUC-12>APLRT1,WIDE1-1,qAR,IW2MUC-10:!/7:sXQ($%_F:Q.../...g...t069r...p...P...h63b09940 Bat=3.95V (74%)