APRS Packet Errors for DG1GMY-17 (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
20260209104526DG1GMY-17>APRSMC,TCPIP*,qAR,DG1GMY-73:!4845.22NM00811.15E#MC/N Bergsee, JN48CS#NiWiS MCN/17/B=100/A=000663
20260209114557DG1GMY-17>APRSMC,TCPIP*,qAR,DG1GMY-73:!4845.22NM00811.15E#MC/N Bergsee, JN48CS#NiWiS MCN/17/B=100/A=000663
20260209121611DG1GMY-17>APRSMC,TCPIP*,qAR,DG1GMY-73:!4845.22NM00811.15E#MC/N Bergsee, JN48CS#NiWiS MCN/17/B=100/A=000663
20260209124628DG1GMY-17>APRSMC,TCPIP*,qAR,DG1GMY-73:!4845.22NM00811.15E#MC/N Bergsee, JN48CS#NiWiS MCN/17/B=100/A=000663
20260209131635DG1GMY-17>APRSMC,TCPIP*,qAR,DG1GMY-73:!4845.22NM00811.15E#MC/N Bergsee, JN48CS#NiWiS MCN/17/B=100/A=000663
20260209134650DG1GMY-17>APRSMC,TCPIP*,qAR,DG1GMY-73:!4845.22NM00811.15E#MC/N Bergsee, JN48CS#NiWiS MCN/17/B=100/A=000663
20260209141702DG1GMY-17>APRSMC,TCPIP*,qAR,DG1GMY-73:!4845.22NM00811.15E#MC/N Bergsee, JN48CS#NiWiS MCN/17/B=100/A=000663
20260209151732DG1GMY-17>APRSMC,TCPIP*,qAR,DG1GMY-73:!4845.22NM00811.15E#MC/N Bergsee, JN48CS#NiWiS MCN/17/B=100/A=000663