APRS Packet Errors for DF2KX-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
20260209085858	DF2KX-12>APRSGW,TCPIP*,qAR,DF2KX-12:!4828.00N/01155.37E##Gerd/B=100/A=001394
20260209092913	DF2KX-12>APRSGW,TCPIP*,qAR,DF2KX-12:!4828.00N/01155.37E##Gerd/B=100/A=001394
20260209095928	DF2KX-12>APRSGW,TCPIP*,qAR,DF2KX-12:!4828.00N/01155.37E##Gerd/B=100/A=001394
20260209102944	DF2KX-12>APRSGW,TCPIP*,qAR,DF2KX-12:!4828.00N/01155.37E##Gerd/B=097/A=001394
20260209105959	DF2KX-12>APRSGW,TCPIP*,qAR,DF2KX-12:!4828.00N/01155.37E##Gerd/B=100/A=001394
20260209113014	DF2KX-12>APRSGW,TCPIP*,qAR,DF2KX-12:!4828.00N/01155.37E##Gerd/B=100/A=001394
20260209120029	DF2KX-12>APRSGW,TCPIP*,qAR,DF2KX-12:!4828.00N/01155.37E##Gerd/B=095/A=001394
20260209123044	DF2KX-12>APRSGW,TCPIP*,qAR,DF2KX-12:!4828.00N/01155.37E##Gerd/B=100/A=001394
20260209130100	DF2KX-12>APRSGW,TCPIP*,qAR,DF2KX-12:!4828.00N/01155.37E##Gerd/B=100/A=001394
20260209133115	DF2KX-12>APRSGW,TCPIP*,qAR,DF2KX-12:!4828.00N/01155.37E##Gerd/B=100/A=001394
20260209140130	DF2KX-12>APRSGW,TCPIP*,qAR,DF2KX-12:!4828.00N/01155.37E##Gerd/B=100/A=001394
20260209143146	DF2KX-12>APRSGW,TCPIP*,qAR,DF2KX-12:!4828.00N/01155.37E##Gerd/B=100/A=001394