APRS Packet Errors for N1DP-5 (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
20260208145331N1DP-5>APN383,W1EMA-1,WIDE2*,qAR,KD1KE:!4438.51NS06810.29W#PHG5350 W3,MEn,Franklin ME
20260208152332N1DP-5>APN383,W1EMA-1,KX1EMA-12,WIDE2*,qAR,KD1KE:!4438.51NS06810.29W#PHG5350 W3,MEn,Franklin ME
20260208155331N1DP-5>APN383,W1EMA-1,WIDE2*,qAR,KD1KE:!4438.51NS06810.29W#PHG5350 W3,MEn,Franklin ME
20260208162331N1DP-5>APN383,W1EMA-1*,WIDE2-1,qAR,KD1KE:!4438.51NS06810.29W#PHG5350 W3,MEn,Franklin ME
20260208165331N1DP-5>APN383,W1EMA-1,WIDE2*,qAR,KD1KE:!4438.51NS06810.29W#PHG5350 W3,MEn,Franklin ME
20260208172332N1DP-5>APN383,W1EMA-1*,WIDE2,qAR,N1JOV-5:!4438.51NS06810.29W#PHG5350 W3,MEn,Franklin ME
20260208182331N1DP-5>APN383,W1EMA-1*,WIDE2-1,qAR,KD1KE:!4438.51NS06810.29W#PHG5350 W3,MEn,Franklin ME
20260208185331N1DP-5>APN383,W1EMA-1,WIDE2*,qAR,KD1KE:!4438.51NS06810.29W#PHG5350 W3,MEn,Franklin ME
20260208192331N1DP-5>APN383,W1EMA-1*,WIDE2-1,qAR,KD1KE:!4438.51NS06810.29W#PHG5350 W3,MEn,Franklin ME
20260208195331N1DP-5>APN383,W1EMA-1,WIDE2*,qAR,KD1KE:!4438.51NS06810.29W#PHG5350 W3,MEn,Franklin ME
20260208202331N1DP-5>APN383,W1EMA-1*,WIDE2-1,qAR,KD1KE:!4438.51NS06810.29W#PHG5350 W3,MEn,Franklin ME