APRS Packet Errors for LD5UT (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
20260208151859LD5UT>APOT30,LD5MT,LD5AV,LD4EG,WIDE3*,qAR,LA8NRA:!6024.39NS00638.06E#PHG2330 W3,NORn Utne Hardanger
20260208155135LD5UT>APOT30,LD5MT,LD5SK,LD5AG,WIDE3*,qAO,LB6EH-10:!6024.39NS00638.06E#PHG2330 W3,NORn Utne Hardanger
20260208162405LD5UT>APOT30,LD5MT,LD5AV,LD4EG,WIDE3*,qAR,LA8NRA:!6024.39NS00638.06E#PHG2330 W3,NORn Utne Hardanger
20260208165641LD5UT>APOT30,LD5MT,LD5AV,LD4EG,WIDE3*,qAR,LA8NRA:!6024.39NS00638.06E#PHG2330 W3,NORn Utne Hardanger
20260208172916LD5UT>APOT30,LD5MT,LD5AV,LD5AG,WIDE3*,qAO,LB6EH-10:!6024.39NS00638.06E#PHG2330 W3,NORn Utne Hardanger
20260208180150LD5UT>APOT30,LD5MT,LD5SK,LD4EG,WIDE3*,qAR,LA8NRA:!6024.39NS00638.06E#PHG2330 W3,NORn Utne Hardanger
20260208183425LD5UT>APOT30,LD5MT,LD5AV,LD4EG,WIDE3*,qAR,LA8NRA:!6024.39NS00638.06E#PHG2330 W3,NORn Utne Hardanger
20260208190659LD5UT>APOT30,LD5MT,LD5SK,LD4EG,WIDE3*,qAR,LA8NRA:!6024.39NS00638.06E#PHG2330 W3,NORn Utne Hardanger
20260208193932LD5UT>APOT30,LD5MT,LD5SK,LD4EG,WIDE3*,qAR,LA8NRA:!6024.39NS00638.06E#PHG2330 W3,NORn Utne Hardanger
20260208201207LD5UT>APOT30,LD5MT,LD5AV,LD4EG,WIDE3*,qAR,LA8NRA:!6024.39NS00638.06E#PHG2330 W3,NORn Utne Hardanger