APRS Packet Errors for SKRADUHF2 (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
20260208200636YM2KY-1>BEACON,TCPIP*,qAS,YM2KY:;SKRADUHF2*111111z4027.37N/03015.27Er 439.175Mhz T110
20260208203738YM2KY-1>BEACON,TCPIP*,qAS,YM2KY:;SKRADUHF2*111111z4027.37N/03015.27Er 439.175Mhz T110
20260208210840YM2KY-1>BEACON,TCPIP*,qAS,YM2KY:;SKRADUHF2*111111z4027.37N/03015.27Er 439.175Mhz T110
20260208213942YM2KY-1>BEACON,TCPIP*,qAS,YM2KY:;SKRADUHF2*111111z4027.37N/03015.27Er 439.175Mhz T110
20260208221043YM2KY-1>BEACON,TCPIP*,qAS,YM2KY:;SKRADUHF2*111111z4027.37N/03015.27Er 439.175Mhz T110
20260208224145YM2KY-1>BEACON,TCPIP*,qAS,YM2KY:;SKRADUHF2*111111z4027.37N/03015.27Er 439.175Mhz T110
20260208231247YM2KY-1>BEACON,TCPIP*,qAS,YM2KY:;SKRADUHF2*111111z4027.37N/03015.27Er 439.175Mhz T110
20260208234349YM2KY-1>BEACON,TCPIP*,qAS,YM2KY:;SKRADUHF2*111111z4027.37N/03015.27Er 439.175Mhz T110
20260209001450YM2KY-1>BEACON,TCPIP*,qAS,YM2KY:;SKRADUHF2*111111z4027.37N/03015.27Er 439.175Mhz T110
20260209004552YM2KY-1>BEACON,TCPIP*,qAS,YM2KY:;SKRADUHF2*111111z4027.37N/03015.27Er 439.175Mhz T110
20260209011654YM2KY-1>BEACON,TCPIP*,qAS,YM2KY:;SKRADUHF2*111111z4027.37N/03015.27Er 439.175Mhz T110
20260209014756YM2KY-1>BEACON,TCPIP*,qAS,YM2KY:;SKRADUHF2*111111z4027.37N/03015.27Er 439.175Mhz T110