APRS Packet Errors for DK1FF-13 (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
20260208181156	DK1FF-13>APTWR,TCPIP*,qAC,APRSTH:!5050.24N/01037.96E- IGate Rx-only 144.800Mhz
20260208184156	DK1FF-13>APTWR,TCPIP*,qAC,APRSTH:!5050.24N/01037.96E- IGate Rx-only 144.800Mhz
20260208191156	DK1FF-13>APTWR,TCPIP*,qAC,APRSTH:!5050.24N/01037.96E- IGate Rx-only 144.800Mhz
20260208194156	DK1FF-13>APTWR,TCPIP*,qAC,APRSTH:!5050.24N/01037.96E- IGate Rx-only 144.800Mhz
20260208201156	DK1FF-13>APTWR,TCPIP*,qAC,APRSTH:!5050.24N/01037.96E- IGate Rx-only 144.800Mhz
20260208204156	DK1FF-13>APTWR,TCPIP*,qAC,APRSTH:!5050.24N/01037.96E- IGate Rx-only 144.800Mhz
20260208211156	DK1FF-13>APTWR,TCPIP*,qAC,APRSTH:!5050.24N/01037.96E- IGate Rx-only 144.800Mhz
20260208214156	DK1FF-13>APTWR,TCPIP*,qAC,APRSTH:!5050.24N/01037.96E- IGate Rx-only 144.800Mhz
20260208221156	DK1FF-13>APTWR,TCPIP*,qAC,APRSTH:!5050.24N/01037.96E- IGate Rx-only 144.800Mhz
20260208224156	DK1FF-13>APTWR,TCPIP*,qAC,APRSTH:!5050.24N/01037.96E- IGate Rx-only 144.800Mhz
20260208231156	DK1FF-13>APTWR,TCPIP*,qAC,APRSTH:!5050.24N/01037.96E- IGate Rx-only 144.800Mhz
20260208234156	DK1FF-13>APTWR,TCPIP*,qAC,APRSTH:!5050.24N/01037.96E- IGate Rx-only 144.800Mhz