APRS Packet Errors for MW3ASG-2 (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
20260208143619MW3ASG-2>APDW17,WIDE2-1,qAO,GB3WB:!b4II@Make# ! MW3ASG APRS Digipeater
20260208145620MW3ASG-2>APDW17,WIDE2-1,qAO,GB3WB:!b4II@Make# ! MW3ASG APRS Digipeater
20260208151619MW3ASG-2>APDW17,WIDE2-1,qAO,GB3WB:!b4II@Make# ! MW3ASG APRS Digipeater
20260208153619MW3ASG-2>APDW17,WIDE2-1,qAO,GB3WB:!b4II@Make# ! MW3ASG APRS Digipeater
20260208155619MW3ASG-2>APDW17,WIDE2-1,qAO,GB3WB:!b4II@Make# ! MW3ASG APRS Digipeater
20260208171620MW3ASG-2>APDW17,WIDE2-1,qAO,GB3WB:!b4II@Make# ! MW3ASG APRS Digipeater
20260208173619MW3ASG-2>APDW17,WIDE2-1,qAO,GB3WB:!b4II@Make# ! MW3ASG APRS Digipeater
20260208175619MW3ASG-2>APDW17,WIDE2-1,qAO,GB3WB:!b4II@Make# ! MW3ASG APRS Digipeater
20260208181619MW3ASG-2>APDW17,WIDE2-1,qAO,GB3WB:!b4II@Make# ! MW3ASG APRS Digipeater
20260208183619MW3ASG-2>APDW17,WIDE2-1,qAO,GB3WB:!b4II@Make# ! MW3ASG APRS Digipeater
20260208185619MW3ASG-2>APDW17,WIDE2-1,qAO,GB3WB:!b4II@Make# ! MW3ASG APRS Digipeater
20260208191619MW3ASG-2>APDW17,WIDE2-1,qAO,GB3WB:!b4II@Make# ! MW3ASG APRS Digipeater
20260208193619MW3ASG-2>APDW17,WIDE2-1,qAO,GB3WB:!b4II@Make# ! MW3ASG APRS Digipeater