APRS Packet Errors for LD2GN (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
20260208145201LD2GN>APOT30,WIDE2-1,qAR,LD2GI:!6059.63NS01120.29E# 12.8V 39C W3, NORn Nordhue/Elverum
20260208152125LD2GN>APOT30,WIDE2-1,qAR,LD2OH:!6059.63NS01120.29E# 12.9V 37C W3, NORn Nordhue/Elverum
20260208155047LD2GN>APOT30,WIDE2-1,qAR,LD2GI:!6059.63NS01120.29E# 12.8V 37C W3, NORn Nordhue/Elverum
20260208162011LD2GN>APOT30,WIDE2-1,qAR,LD2GI:!6059.63NS01120.29E# 12.9V 37C W3, NORn Nordhue/Elverum
20260208164937LD2GN>APOT30,WIDE2-1,qAR,LD2GI:!6059.63NS01120.29E# 12.7V 37C W3, NORn Nordhue/Elverum
20260208171904LD2GN>APOT30,WIDE2-1,qAR,LD2GI:!6059.63NS01120.29E# 12.8V 38C W3, NORn Nordhue/Elverum
20260208174832LD2GN>APOT30,WIDE2-1,qAR,LD2OH:!6059.63NS01120.29E# 12.8V 37C W3, NORn Nordhue/Elverum
20260208181748LD2GN>APOT30,LB1WJ-1*,WIDE2,qAO,LB1WJ-9:!6059.63NS01120.29E# 12.9V 38C W3, NORn Nordhue/Elverum
20260208184706LD2GN>APOT30,LB1WJ-1*,WIDE2,qAO,LB1WJ-9:!6059.63NS01120.29E# 12.9V 37C W3, NORn Nordhue/Elverum
20260208191629LD2GN>APOT30,WIDE2-1,qAR,SM4XFJ-1:!6059.63NS01120.29E# 12.6V 37C W3, NORn Nordhue/Elverum
20260208194557LD2GN>APOT30,WIDE2-1,qAR,SM4XFJ-1:!6059.63NS01120.29E# 12.9V 38C W3, NORn Nordhue/Elverum
20260208201516LD2GN>APOT30,WIDE2-1,qAR,SM4XFJ-1:!6059.63NS01120.29E# 12.9V 39C W3, NORn Nordhue/Elverum