APRS Packet Errors for N3JHS (last 24 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
20260731132219	N3JHS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3JHS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NewYork MMDVM 433.2000 MHz
20260731135252	N3JHS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3JHS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NewYork MMDVM 433.2000 MHz
20260731142331	N3JHS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3JHS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NewYork MMDVM 433.2000 MHz
20260731145404	N3JHS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3JHS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NewYork MMDVM 433.2000 MHz
20260731152438	N3JHS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3JHS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NewYork MMDVM 433.2000 MHz
20260731155510	N3JHS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3JHS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NewYork MMDVM 433.2000 MHz
20260731161233	N3JHS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3JHS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NewYork MMDVM 433.2000 MHz