APRS Packet Errors for F1CNB-4 (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
20260209153506F1CNB-4>WIDE1-1,F8KII-4*,WIDE2-1,qAR,F8KII-6:!4931.52N/00015.79E#F1CNB ADRASEC76
20260209161105F1CNB-4>WIDE1-1,F8KII-4*,WIDE2-1,qAR,F8KII-6:!4931.52N/00015.79E#F1CNB ADRASEC76
20260209163812F1CNB-4>WIDE1-1,F8KII-4*,WIDE2-1,qAR,F8KII-6:!4931.52N/00015.79E#F1CNB ADRASEC76
20260209165923F1CNB-4>WIDE1-1,F8KII-4*,WIDE2-1,qAR,F8KII-6:!4931.52N/00015.79E#F1CNB ADRASEC76
20260209170332F1CNB-4>WIDE1-1,WIDE2-2,qAO,F1ZNV-4:!4931.52N/00015.79E#F1CNB ADRASEC76
20260209170538F1CNB-4>WIDE1-1,WIDE2-2,qAO,F1ZNV-4:!4931.52N/00015.79E#F1CNB ADRASEC76
20260209170740F1CNB-4>WIDE1-1,WIDE2-2,qAO,F1ZNV-4:!4931.52N/00015.79E#F1CNB ADRASEC76
20260209171152F1CNB-4>WIDE1-1,WIDE2-2,qAO,F1ZNV-4:!4931.52N/00015.79E#F1CNB ADRASEC76
20260209171401F1CNB-4>WIDE1-1,WIDE2-2,qAO,F1ZNV-4:!4931.52N/00015.79E#F1CNB ADRASEC76
20260209172849F1CNB-4>WIDE1-1,WIDE2-2,qAO,F1ZNV-4:!4931.52N/00015.79E#F1CNB ADRASEC76
20260209182118F1CNB-4>WIDE1-1,WIDE2-2,qAO,F1ZNV-4:!4931.52N/00015.79E#F1CNB ADRASEC76
20260209185246F1CNB-4>WIDE1-1,WIDE2-2,qAO,F1ZNV-4:!4931.52N/00015.79E#F1CNB ADRASEC76
20260209190524F1CNB-4>WIDE1-1,WIDE2-2,qAO,F1ZNV-4:!4931.52N/00015.79E#F1CNB ADRASEC76
20260209190734F1CNB-4>WIDE1-1,F8KII-4*,WIDE2-1,qAR,F8KII-6:!4931.52N/00015.79E#F1CNB ADRASEC76