APRS Packet Errors for SV1HBJ (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
20240508214720SV1HBJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1HBJ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 433.9000 MHz
20240508221823SV1HBJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1HBJ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 433.9000 MHz
20240508224926SV1HBJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1HBJ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 433.9000 MHz
20240508232027SV1HBJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1HBJ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 433.9000 MHz
20240508235129SV1HBJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1HBJ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 433.9000 MHz
20240509002231SV1HBJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1HBJ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 433.9000 MHz
20240509005333SV1HBJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1HBJ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 433.9000 MHz
20240509012436SV1HBJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1HBJ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 433.9000 MHz
20240509015538SV1HBJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1HBJ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 433.9000 MHz
20240509025740SV1HBJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1HBJ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 433.9000 MHz