APRS Packet Errors for ON1ARF-10 (last 24 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
20250711060711ON1ARF-10>APLRG1,WIDE2-1,qAO,ON2ACO-23:!testing heltec tracker
20250711072212ON1ARF-10>APLRG1,WIDE2-1,qAO,ON7DKE-10:!testing heltec tracker
20250711085217ON1ARF-10>APLRG1,WIDE2-1,qAO,ON7DKE-10:!testing heltec tracker
20250711100718ON1ARF-10>APLRG1,WIDE2-1,qAO,ON2ACO-23:!testing heltec tracker
20250711112219ON1ARF-10>APLRG1,WIDE2-1,qAO,ON2ACO-23:!testing heltec tracker
20250711142222ON1ARF-10>APLRG1,WIDE2-1,qAO,ON2ACO-11:!testing heltec tracker
20250711165224ON1ARF-10>APLRG1,WIDE2-1,qAO,ON2ACO-23:!testing heltec tracker
20250711175225ON1ARF-10>APLRG1,WIDE2-1,qAO,ON2ACO-23:!testing heltec tracker
20250711190726ON1ARF-10>APLRG1,WIDE2-1,qAR,M0LMK-10:!testing heltec tracker
20250711203727ON1ARF-10>APLRG1,WIDE2-1,qAO,ON2ACO-11:!testing heltec tracker
20250711215228ON1ARF-10>APLRG1,WIDE2-1,qAO,ON2ACO-23:!testing heltec tracker
20250711225229ON1ARF-10>APLRG1,WIDE2-1,qAO,ON2ACO-23:!testing heltec tracker
20250712000730ON1ARF-10>APLRG1,WIDE2-1,qAO,ON7DKE-10:!testing heltec tracker
20250712005241ON1ARF-10>APLRG1,WIDE2-1,qAO,ON7DKE-10:!testing heltec tracker
20250712020733ON1ARF-10>APLRG1,WIDE2-1,qAO,ON2ACO-23:!testing heltec tracker
20250712050736ON1ARF-10>APLRG1,WIDE2-1,qAO,ON2ACO-23:!testing heltec tracker