APRS Packet Errors for SV6N (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
20241023001742SV6N>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6N-DP!0000.00N/00000.00ErRNG0034 IPSC2-GR-DMO Hytera 438.9625@-7.6 MHz
20241023004849SV6N>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6N-DP!0000.00N/00000.00ErRNG0034 IPSC2-GR-DMO Hytera 438.9625@-7.6 MHz
20241023011959SV6N>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6N-DP!0000.00N/00000.00ErRNG0034 IPSC2-GR-DMO Hytera 438.9625@-7.6 MHz
20241023015106SV6N>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6N-DP!0000.00N/00000.00ErRNG0034 IPSC2-GR-DMO Hytera 438.9625@-7.6 MHz
20241023022214SV6N>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6N-DP!0000.00N/00000.00ErRNG0034 IPSC2-GR-DMO Hytera 438.9625@-7.6 MHz
20241023025320SV6N>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6N-DP!0000.00N/00000.00ErRNG0034 IPSC2-GR-DMO Hytera 438.9625@-7.6 MHz
20241023035533SV6N>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6N-DP!0000.00N/00000.00ErRNG0034 IPSC2-GR-DMO Hytera 438.9625@-7.6 MHz
20241023042639SV6N>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6N-DP!0000.00N/00000.00ErRNG0034 IPSC2-GR-DMO Hytera 438.9625@-7.6 MHz
20241023045745SV6N>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6N-DP!0000.00N/00000.00ErRNG0034 IPSC2-GR-DMO Hytera 438.9625@-7.6 MHz
20241023052853SV6N>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6N-DP!0000.00N/00000.00ErRNG0034 IPSC2-GR-DMO Hytera 438.9625@-7.6 MHz