APRS Packet Errors for OK2ZK-15 (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
20260208151639OK2ZK-15>APDR16,TCPIP*,qAC,T2DENMARK:=4946.23N1805.39E0145.525MHz D1 nr Exit 342
20260208154154OK2ZK-15>APDR16,TCPIP*,qAC,T2DENMARK:=4946.23N1805.39E0145.525MHz D1 nr Exit 342
20260208160847OK2ZK-15>APDR16,TCPIP*,qAC,T2DENMARK:=4946.23N1805.39E0145.525MHz D1 nr Exit 342
20260208172547OK2ZK-15>APDR16,TCPIP*,qAC,T2DENMARK:=4946.23N1805.39E0145.525MHz D1 nr Exit 342
20260208175552OK2ZK-15>APDR16,TCPIP*,qAC,T2DENMARK:=4946.23N1805.39E0145.525MHz D1 nr Exit 342
20260208182653OK2ZK-15>APDR16,TCPIP*,qAC,T2DENMARK:=4946.23N1805.39E0145.525MHz D1 nr Exit 342
20260208185309OK2ZK-15>APDR16,TCPIP*,qAC,T2DENMARK:=4946.23N1805.39E0145.525MHz D1 nr Exit 342
20260208191924OK2ZK-15>APDR16,TCPIP*,qAC,T2DENMARK:=4946.23N1805.39E0145.525MHz D1 nr Exit 342
20260208194503OK2ZK-15>APDR16,TCPIP*,qAC,T2DENMARK:=4946.23N1805.39E0145.525MHz D1 nr Exit 342
20260208201119OK2ZK-15>APDR16,TCPIP*,qAC,T2DENMARK:=4946.23N1805.39E0145.525MHz D1 nr Exit 342
20260208203619OK2ZK-15>APDR16,TCPIP*,qAC,T2DENMARK:=4946.23N1805.39E0145.525MHz D1 nr Exit 342