APRS Packet Errors for HB9XBO-41 (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
20260209091855HB9XBO-41>APRSMC,TCPIP*,qAR,HB9XBO-40:!4722.72N/00804.51E[MeshCom TDeck+#HB9XBO-41/B=100/A=001299
20260209101647HB9XBO-41>APRSMC,TCPIP*,qAR,HB9XBO-40:!4722.72N/00804.52E[MeshCom TDeck+#HB9XBO-41/B=084/A=001086
20260209104702HB9XBO-41>APRSMC,TCPIP*,qAR,HB9XBO-40:!4722.72N/00804.52E[MeshCom TDeck+#HB9XBO-41/B=076/A=001086
20260209111717HB9XBO-41>APRSMC,TCPIP*,qAR,HB9XBO-40:!4722.72N/00804.52E[MeshCom TDeck+#HB9XBO-41/B=068/A=001086
20260209114732HB9XBO-41>APRSMC,TCPIP*,qAR,HB9XBO-40:!4722.72N/00804.52E[MeshCom TDeck+#HB9XBO-41/B=061/A=001086
20260209121747HB9XBO-41>APRSMC,TCPIP*,qAR,HB9XBO-40:!4722.72N/00804.52E[MeshCom TDeck+#HB9XBO-41/B=053/A=001086
20260209124802HB9XBO-41>APRSMC,TCPIP*,qAR,HB9XBO-40:!4722.72N/00804.52E[MeshCom TDeck+#HB9XBO-41/B=048/A=001086
20260209131819HB9XBO-41>APRSMC,TCPIP*,qAR,HB9XBO-40:!4722.72N/00804.52E[MeshCom TDeck+#HB9XBO-41/B=042/A=001086
20260209134832HB9XBO-41>APRSMC,TCPIP*,qAR,HB9XBO-40:!4722.72N/00804.52E[MeshCom TDeck+#HB9XBO-41/B=036/A=001086
20260209141847HB9XBO-41>APRSMC,TCPIP*,qAR,HB9XBO-40:!4722.72N/00804.52E[MeshCom TDeck+#HB9XBO-41/B=100/A=001086
20260209144902HB9XBO-41>APRSMC,TCPIP*,qAR,HB9XBO-40:!4722.72N/00804.52E[MeshCom TDeck+#HB9XBO-41/B=100/A=001086