APRS Packet Errors for DO1FJD-9 (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
20260209105723DO1FJD-9>APLT00-1,qAO,DH5NT-10:!5145.83NL00924.03E>309/045/A=000000LoRa APRS Tracker Franz on Tour DOK H34
20260209105919DO1FJD-9>APLT00-1,qAO,DH5NT-10:!5146.44NL00922.87E>284/013/A=000377
20260209110631DO1FJD-9>APLT00-1,qAO,DO1SKP-10:!5146.32NL00922.82E>195/016/A=000000LoRa APRS Tracker Franz on Tour DOK H34
20260209110704DO1FJD-9>APLT00-1,qAO,DH5NT-10:!5146.21NL00922.75E>151/001/A=000347
20260209110741DO1FJD-9>APLT00-1,qAO,DH5NT-10:!5146.17NL00922.74E>176/017/A=000357
20260209110814DO1FJD-9>APLT00-1,qAO,DO1SGH-11:!5146.09NL00922.58E>299/013/A=000352
20260209110857DO1FJD-9>APLT00-1,qAO,DO1SKP-10:!5146.19NL00922.37E>327/005/A=000362
20260209110932DO1FJD-9>APLT00-1,qAO,DH5NT-10:!5146.30NL00922.34E>302/011/A=000378
20260209111005DO1FJD-9>APLT00-1,qAO,DH5NT-10:!5146.40NL00922.22E>341/001/A=000368
20260209111038DO1FJD-9>APLT00-1,qAO,DH5NT-10:!5146.36NL00922.06E>246/014/A=000387
20260209111111DO1FJD-9>APLT00-1,qAO,DH5NT-10:!5146.34NL00922.01E>084/002/A=000396