APRS Packet Errors for JF0WBW-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
20260208132449JF0WBW-12>APDR10,WIDE1-1,qAR,JR0ZFI-10:!3614.39N/13752.92E[337/000/A=002046from DJ-MD5 DMR tansceiver
20260208133308JF0WBW-12>APDR10,WIDE1-1,qAR,JR0ZFI-10:!3614.38N/13752.92E[337/000/A=001998from DJ-MD5 DMR tansceiver
20260208135409JF0WBW-12>APDR10,WIDE1-1,qAR,JR0ZFI-10:!3614.39N/13752.90E[131/002/A=001614from DJ-MD5 DMR tansceiver
20260208135811JF0WBW-12>APDR10,WIDE1-1,qAR,JR0ZFI-10:!3614.39N/13752.92E[131/000/A=001920from DJ-MD5 DMR tansceiver
20260208140232JF0WBW-12>APDR10,WIDE1-1,qAR,JR0ZFI-10:!3614.39N/13752.93E[131/000/A=001932from DJ-MD5 DMR tansceiver
20260208140637JF0WBW-12>APDR10,WIDE1-1,qAR,JR0ZFI-10:!3614.39N/13752.93E[133/002/A=001677from DJ-MD5 DMR tansceiver
20260208141038JF0WBW-12>APDR10,WIDE1-1,qAR,JR0ZFI-10:!3614.42N/13752.91E[133/003/A=001080from DJ-MD5 DMR tansceiver
20260208141439JF0WBW-12>APDR10,WIDE1-1,qAR,JR0ZFI-10:!3614.43N/13752.89E[131/000/A=001083from DJ-MD5 DMR tansceiver
20260208143055JF0WBW-12>APDR10,WIDE1-1,qAR,JR0ZFI-10:!3614.36N/13752.92E[192/000/A=001440from DJ-MD5 DMR tansceiver