APRS Packet Errors for DK9HI-11 (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
20260209105854DK9HI-11>APRSMC,TCPIP*,qAR,DL5OCD-6:!5223.30N/00959.17E#/B=100/A=000203
20260209112907DK9HI-11>APRSMC,TCPIP*,qAR,DL5OCD-6:!5223.30N/00959.17E#/B=100/A=000203
20260209115932DK9HI-11>APRSMC,TCPIP*,qAR,DL5OCD-6:!5223.30N/00959.17E#/B=100/A=000203
20260209122940DK9HI-11>APRSMC,TCPIP*,qAR,DL5OCD-6:!5223.30N/00959.17E#/B=100/A=000203
20260209125959DK9HI-11>APRSMC,TCPIP*,qAR,DL5OCD-6:!5223.30N/00959.17E#/B=100/A=000203
20260209133010DK9HI-11>APRSMC,TCPIP*,qAR,DL5OCD-6:!5223.30N/00959.17E#/B=100/A=000203
20260209140026DK9HI-11>APRSMC,TCPIP*,qAR,DL5OCD-6:!5223.30N/00959.17E#/B=100/A=000203
20260209143040DK9HI-11>APRSMC,TCPIP*,qAR,DL5OCD-6:!5223.30N/00959.17E#/B=100/A=000203
20260209150105DK9HI-11>APRSMC,TCPIP*,qAR,DL5OCD-6:!5223.30N/00959.17E#/B=100/A=000203
20260209153117DK9HI-11>APRSMC,TCPIP*,qAR,DL5OCD-6:!5223.30N/00959.17E#/B=100/A=000203
20260209160130DK9HI-11>APRSMC,TCPIP*,qAR,DL5OCD-6:!5223.30N/00959.17E#/B=100/A=000203
20260209163144DK9HI-11>APRSMC,TCPIP*,qAR,DL5OCD-6:!5223.30N/00959.17E#/B=100/A=000203