APRS Packet Errors for DN9SE-12 (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
20260208181830DN9SE-12>APRSGW,TCPIP*,qAR,DN9SE-12:!5049.77N/00802.14E#/B=006/A=000984
20260208184845DN9SE-12>APRSGW,TCPIP*,qAR,DN9SE-12:!5049.77N/00802.14E#/B=075/A=000984
20260208191859DN9SE-12>APRSGW,TCPIP*,qAR,DN9SE-12:!5049.77N/00802.14E#/B=023/A=000984
20260208194914DN9SE-12>APRSGW,TCPIP*,qAR,DN9SE-12:!5049.77N/00802.14E#/B=031/A=000984
20260208201929DN9SE-12>APRSGW,TCPIP*,qAR,DN9SE-12:!5049.77N/00802.14E#/B=091/A=000984
20260208204946DN9SE-12>APRSGW,TCPIP*,qAR,DN9SE-12:!5049.77N/00802.14E#/B=010/A=000984
20260208212001DN9SE-12>APRSGW,TCPIP*,qAR,DN9SE-12:!5049.77N/00802.14E#/B=100/A=000984
20260208215013DN9SE-12>APRSGW,TCPIP*,qAR,DN9SE-12:!5049.77N/00802.14E#/B=100/A=000984
20260208222028DN9SE-12>APRSGW,TCPIP*,qAR,DN9SE-12:!5049.77N/00802.14E#/B=023/A=000984
20260208225043DN9SE-12>APRSGW,TCPIP*,qAR,DN9SE-12:!5049.77N/00802.14E#/B=075/A=000984
20260208232058DN9SE-12>APRSGW,TCPIP*,qAR,DN9SE-12:!5049.77N/00802.14E#/B=100/A=000984
20260208235115DN9SE-12>APRSGW,TCPIP*,qAR,DN9SE-12:!5049.77N/00802.14E#/B=096/A=000984