APRS Packet Errors for DK0HQ-10 (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
20260209093248DK0HQ-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4p19P<-=# !GIGAFU-Bonn.de 438,850MHz
20260209094748DK0HQ-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4p19P<-=# !GIGAFU-Bonn.de 438,850MHz
20260209100248DK0HQ-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4p19P<-=# !GIGAFU-Bonn.de 438,850MHz
20260209101748DK0HQ-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4p19P<-=# !GIGAFU-Bonn.de 438,850MHz
20260209103248DK0HQ-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4p19P<-=# !GIGAFU-Bonn.de 438,850MHz
20260209104748DK0HQ-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4p19P<-=# !GIGAFU-Bonn.de 438,850MHz
20260209110248DK0HQ-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4p19P<-=# !GIGAFU-Bonn.de 438,850MHz
20260209111749DK0HQ-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4p19P<-=# !GIGAFU-Bonn.de 438,850MHz
20260209113249DK0HQ-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4p19P<-=# !GIGAFU-Bonn.de 438,850MHz
20260209114749DK0HQ-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4p19P<-=# !GIGAFU-Bonn.de 438,850MHz
20260209120250DK0HQ-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4p19P<-=# !GIGAFU-Bonn.de 438,850MHz
20260209121749DK0HQ-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4p19P<-=# !GIGAFU-Bonn.de 438,850MHz
20260209123249DK0HQ-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4p19P<-=# !GIGAFU-Bonn.de 438,850MHz
20260209124749DK0HQ-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4p19P<-=# !GIGAFU-Bonn.de 438,850MHz
20260209130249DK0HQ-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4p19P<-=# !GIGAFU-Bonn.de 438,850MHz
20260209131749DK0HQ-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4p19P<-=# !GIGAFU-Bonn.de 438,850MHz
20260209133249DK0HQ-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4p19P<-=# !GIGAFU-Bonn.de 438,850MHz
20260209134749DK0HQ-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4p19P<-=# !GIGAFU-Bonn.de 438,850MHz
20260209140249DK0HQ-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4p19P<-=# !GIGAFU-Bonn.de 438,850MHz
20260209141749DK0HQ-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4p19P<-=# !GIGAFU-Bonn.de 438,850MHz
20260209143249DK0HQ-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4p19P<-=# !GIGAFU-Bonn.de 438,850MHz
20260209144750DK0HQ-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4p19P<-=# !GIGAFU-Bonn.de 438,850MHz
20260209150249DK0HQ-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4p19P<-=# !GIGAFU-Bonn.de 438,850MHz
20260209151749DK0HQ-10>APLRG1,TCPIP*,qAC,T2CHILE:!L4p19P<-=# !GIGAFU-Bonn.de 438,850MHz