APRS Packet Errors for DN7TMU-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
20260209130651DN7TMU-12>APRSGW,TCPIP*,qAR,DN7TMU-12:!4839.22N/00911.85E#/B=100
20260209133706DN7TMU-12>APRSGW,TCPIP*,qAR,DN7TMU-12:!4839.22N/00911.85E#/B=100
20260209140725DN7TMU-12>APRSGW,TCPIP*,qAR,DN7TMU-12:!4839.22N/00911.85E#/B=100
20260209143740DN7TMU-12>APRSGW,TCPIP*,qAR,DN7TMU-12:!4839.22N/00911.85E#/B=100
20260209150755DN7TMU-12>APRSGW,TCPIP*,qAR,DN7TMU-12:!4839.22N/00911.85E#/B=100
20260209153810DN7TMU-12>APRSGW,TCPIP*,qAR,DN7TMU-12:!4839.22N/00911.85E#/B=100
20260209160828DN7TMU-12>APRSGW,TCPIP*,qAR,DN7TMU-12:!4839.22N/00911.85E#/B=100
20260209163843DN7TMU-12>APRSGW,TCPIP*,qAR,DN7TMU-12:!4839.22N/00911.85E#/B=097
20260209170858DN7TMU-12>APRSGW,TCPIP*,qAR,DN7TMU-12:!4839.22N/00911.85E#/B=097
20260209170932DN7TMU-12>APRSMC,TCPIP*,qAR,DL1ZP-12:!4839.22N/00911.85E#/B=097
20260209173914DN7TMU-12>APRSGW,TCPIP*,qAR,DN7TMU-12:!4839.22N/00911.85E#/B=100
20260209180929DN7TMU-12>APRSGW,TCPIP*,qAR,DN7TMU-12:!4839.22N/00911.85E#/B=100
20260209183944DN7TMU-12>APRSGW,TCPIP*,qAR,DN7TMU-12:!4839.22N/00911.85E#/B=100