APRS Packet Errors for N0JLF-10 (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
20260209123111	N0JLF-10>APDW17,WIDE1-1,qAR,W4CAT-1:!3623.50NI08608.43W#PHG9150444.950Mhz T118 +5.0Mhz KM4GHM Repeater - N0JLF DIGI/IGATE in Hartsville
20260209130111	N0JLF-10>APDW17,WIDE1-1,qAR,W4CAT-1:!3623.50NI08608.43W#PHG9150444.950Mhz T118 +5.0Mhz KM4GHM Repeater - N0JLF DIGI/IGATE in Hartsville
20260209143113	N0JLF-10>APDW17,WIDE1-1,qAR,W4CAT-1:!3623.50NI08608.43W#PHG9150444.950Mhz T118 +5.0Mhz KM4GHM Repeater - N0JLF DIGI/IGATE in Hartsville
20260209153111	N0JLF-10>APDW17,WIDE1-1,qAR,W4CAT-1:!3623.50NI08608.43W#PHG9150444.950Mhz T118 +5.0Mhz KM4GHM Repeater - N0JLF DIGI/IGATE in Hartsville
20260209160111	N0JLF-10>APDW17,WIDE1-1,qAR,W4CAT-1:!3623.50NI08608.43W#PHG9150444.950Mhz T118 +5.0Mhz KM4GHM Repeater - N0JLF DIGI/IGATE in Hartsville
20260209163111	N0JLF-10>APDW17,WIDE1-1,qAR,W4CAT-1:!3623.50NI08608.43W#PHG9150444.950Mhz T118 +5.0Mhz KM4GHM Repeater - N0JLF DIGI/IGATE in Hartsville
20260209170111	N0JLF-10>APDW17,WIDE1-1,qAR,W4CAT-1:!3623.50NI08608.43W#PHG9150444.950Mhz T118 +5.0Mhz KM4GHM Repeater - N0JLF DIGI/IGATE in Hartsville
20260209173111	N0JLF-10>APDW17,WIDE1-1,qAR,W4CAT-1:!3623.50NI08608.43W#PHG9150444.950Mhz T118 +5.0Mhz KM4GHM Repeater - N0JLF DIGI/IGATE in Hartsville