APRS Packet Errors for R3DNL-Y (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
20260327183709	R3DNL-Y>APDPRS,C4FM*,qAR,RV2H-N:!0000.00N/00000.00E- 0x35 via MMDVM
20260327183749	R3DNL-Y>APDPRS,C4FM*,qAR,RV2H-N:!0000.00N/00000.00E- 0x35 via MMDVM
20260327183829	R3DNL-Y>APDPRS,C4FM*,qAR,RV2H-N:!0000.00N/00000.00E- 0x35 via MMDVM
20260327183939	R3DNL-Y>APDPRS,C4FM*,qAR,RV2H-N:!0000.00N/00000.00E- 0x35 via MMDVM
20260327184109	R3DNL-Y>APDPRS,C4FM*,qAR,RV2H-N:!0000.00N/00000.00E- 0x35 via MMDVM
20260327184319	R3DNL-Y>APDPRS,C4FM*,qAR,RV2H-N:!0000.00N/00000.00E- 0x35 via MMDVM
20260327184419	R3DNL-Y>APDPRS,C4FM*,qAR,RV2H-N:!0000.00N/00000.00E- 0x35 via MMDVM
20260327201509	R3DNL-Y>APDPRS,C4FM*,qAR,RV2H-N:!0000.00N/00000.00E- 0x35 via MMDVM