APRS Packet Errors for OE6DMD-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
20260209120856OE6DMD-12>APRSGW,TCPIP*,qAR,OE6DMD-12:!4724.82N/01515.61E#/B=094/A=001778
20260209123911OE6DMD-12>APRSGW,TCPIP*,qAR,OE6DMD-12:!4724.82N/01515.61E#/B=100/A=001778
20260209130926OE6DMD-12>APRSGW,TCPIP*,qAR,OE6DMD-12:!4724.82N/01515.61E#/B=100/A=001778
20260209133944OE6DMD-12>APRSGW,TCPIP*,qAR,OE6DMD-12:!4724.82N/01515.61E#/B=100/A=001778
20260209140959OE6DMD-12>APRSGW,TCPIP*,qAR,OE6DMD-12:!4724.82N/01515.61E#/B=096/A=001778
20260209144014OE6DMD-12>APRSGW,TCPIP*,qAR,OE6DMD-12:!4724.82N/01515.61E#/B=100/A=001778
20260209151029OE6DMD-12>APRSGW,TCPIP*,qAR,OE6DMD-12:!4724.82N/01515.61E#/B=100/A=001778
20260209154048OE6DMD-12>APRSGW,TCPIP*,qAR,OE6DMD-12:!4724.82N/01515.61E#/B=100/A=001778
20260209161103OE6DMD-12>APRSGW,TCPIP*,qAR,OE6DMD-12:!4724.82N/01515.61E#/B=100/A=001778
20260209164114OE6DMD-12>APRSGW,TCPIP*,qAR,OE6DMD-12:!4724.82N/01515.61E#/B=100/A=001778
20260209171129OE6DMD-12>APRSGW,TCPIP*,qAR,OE6DMD-12:!4724.82N/01515.61E#/B=093/A=001778
20260209174144OE6DMD-12>APRSGW,TCPIP*,qAR,OE6DMD-12:!4724.82N/01515.61E#/B=100/A=001778