APRS Packet Errors for DL1MAG-7 (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
20260208162258DL1MAG-7>APAT81-1,WIDE1-1,WIDE2-1,qAS,DB0ND-10:!4931.26N/00755.35E[235/031/A=000000MaG on Route/DL1MAG
20260208162714DL1MAG-7>APAT81-1,WIDE1-1,WIDE2-1,qAS,DB0ND-10:!4931.26N/00755.35E[235/031/A=000000MaG on Route/DL1MAG
20260208162916DL1MAG-7>APAT81-1,WIDE1-1,WIDE2-1,qAS,DB0ND-10:!4931.26N/00755.35E[235/031/A=000000MaG on Route/DL1MAG
20260208164342DL1MAG-7>APAT81-1,WIDE1-1,WIDE2-1,qAS,DB0ND-10:!4931.26N/00755.35E[235/031/A=000000MaG on Route/DL1MAG
20260208165808DL1MAG-7>APAT81-1,WIDE1-1,WIDE2-1,qAS,DB0ND-10:!4931.26N/00755.35E[235/031/A=000000MaG on Route/DL1MAG
20260208171532DL1MAG-7>APAT81-1,WIDE1-1,WIDE2-1,qAS,DB0ND-10:!4931.26N/00755.35E[235/031/A=000000MaG on Route/DL1MAG
20260208171734DL1MAG-7>APAT81-1,WIDE1-1,WIDE2-1,qAS,DB0ND-10:!4931.26N/00755.35E[235/031/A=000000MaG on Route/DL1MAG
20260208182745DL1MAG-7>APAT81-1,WIDE1-1,WIDE2-1,qAR,DB0SLB-10:!4931.26N/00755.35E[235/031/A=000000MaG on Route/DL1MAG