APRS Packet Errors for LB3LJ-1 (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
20260208200202LB3LJ-1>APAVT5,LD2GN*,WIDE2-1,qAR,LD2OH:=6041.15N/01120.37E#148/000/A=000667Digi. 4.25V
20260208203203LB3LJ-1>APAVT5,LD2GN*,WIDE2-1,qAR,SM4XFJ-1:=6041.15N/01120.37E#221/001/A=000617Digi. 4.24V
20260208210204LB3LJ-1>APAVT5,LD2GN*,WIDE2-1,qAR,LD2OH:=6041.16N/01120.39E#197/000/A=000722Digi. 4.23V
20260208213205LB3LJ-1>APAVT5,LD2GN*,WIDE2-1,qAR,LD2GI:=6041.15N/01120.41E#242/001/A=000620Digi. 4.22V
20260208220206LB3LJ-1>APAVT5,LD2GN*,WIDE2-1,qAR,LD2GI:=6041.16N/01120.39E#243/000/A=000744Digi. 4.21V
20260208230208LB3LJ-1>APAVT5,LD2GN*,WIDE2-1,qAR,LD2GI:=6041.15N/01120.39E#108/000/A=000639Digi. 4.19V
20260209000212LB3LJ-1>APAVT5,LD2GN*,WIDE2-1,qAR,LD2GI:=6041.14N/01120.39E#092/000/A=000604Digi. 4.16V
20260209003211LB3LJ-1>APAVT5,LD2GN*,WIDE2-1,qAR,LD2OH:=6041.15N/01120.38E#322/000/A=000598Digi. 4.16V
20260209010212LB3LJ-1>APAVT5,LD2GN*,WIDE2-1,qAR,LD2GI:=6041.16N/01120.39E#056/000/A=000754Digi. 4.16V