APRS Packet Errors for WB5PJB-44 (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
20250826233641WB5PJB-44>APLRT1,WIDE1-1,qAR,AB0WV-40:!/:OjR3{><_PrQ.../...g...t077r...p...P...h27b08220
20250826234645WB5PJB-44>APLRT1,WIDE1-1,qAO,WB5PJB-55:!/:Vqg3{,f_Q%Q.../...g...t076r...p...P...h29b08170
20250826235648WB5PJB-44>APLRT1,WIDE1-1,qAO,K8ZTT-40:!/:W+T4!UC_QAQ.../...g...t075r...p...P...h26b08050
20250827130439WB5PJB-44>APLRT1,WIDE1-1,qAR,KC0JMW:!/:U6A3{Ic_Q.Q.../...g...t069r...p...P...h39b08100
20250827131443WB5PJB-44>APLRT1,WIDE1-1,qAR,AB0WV-40:!/:P4_3{%E_PwQ.../...g...t070r...p...P...h37b08180