APRS Packet Errors for DK4RS-22 (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
20260208151802DK4RS-22>APRSMC,TCPIP*,qAR,DK4RS-20:!4959.05NM00814.51E#DK4RS-22/B=100/A=000443
20260208154803DK4RS-22>APRSMC,TCPIP*,qAR,DK4RS-20:!4959.05NM00814.51E#DK4RS-22/B=100/A=000505
20260208161802DK4RS-22>APRSMC,TCPIP*,qAR,DK4RS-20:!4959.05NM00814.51E#DK4RS-22/B=100/A=000413
20260208164810DK4RS-22>APRSMC,TCPIP*,qAR,DK4RS-20:!4959.05NM00814.51E#DK4RS-22/B=100/A=000407
20260208171802DK4RS-22>APRSMC,TCPIP*,qAR,DK4RS-20:!4959.05NM00814.50E#DK4RS-22/B=100/A=000397
20260208171945DK4RS-22>APRSMC,TCPIP*,qAR,DG3FAW-12:!4959.05NM00814.50E#DK4RS-22/B=100/A=000397
20260208174803DK4RS-22>APRSMC,TCPIP*,qAR,DK4RS-20:!4959.05NM00814.50E#DK4RS-22/B=100/A=000400
20260208201814DK4RS-22>APRSMC,TCPIP*,qAR,DK4RS-20:!4959.05NM00814.51E#DK4RS-22/B=100/A=000364
20260208204803DK4RS-22>APRSMC,TCPIP*,qAR,DK4RS-20:!4959.05NM00814.49E#DK4RS-22/B=100/A=000410