APRS Packet Errors for W6BXN-3 (last 24 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
20251214215212W6BXN-3>BEACON,qAO,KN6PTO-2:;147.030+x3732.15N/12003.80Wr147.030MHz T100 + R60m Bullion W6BXN
20251214235212W6BXN-3>BEACON,qAO,KN6PTO-2:;147.030+x3732.15N/12003.80Wr147.030MHz T100 + R60m Bullion W6BXN
20251215015213W6BXN-3>BEACON,qAO,KN6PTO-2:;147.030+x3732.15N/12003.80Wr147.030MHz T100 + R60m Bullion W6BXN
20251215035213W6BXN-3>BEACON,qAR,KJ6HUP:;147.030+x3732.15N/12003.80Wr147.030MHz T100 + R60m Bullion W6BXN
20251215055213W6BXN-3>BEACON,qAR,AA6I-1:;147.030+x3732.15N/12003.80Wr147.030MHz T100 + R60m Bullion W6BXN
20251215095213W6BXN-3>BEACON,qAR,KJ6HUP:;147.030+x3732.15N/12003.80Wr147.030MHz T100 + R60m Bullion W6BXN
20251215115213W6BXN-3>BEACON,qAR,KJ6HUP:;147.030+x3732.15N/12003.80Wr147.030MHz T100 + R60m Bullion W6BXN
20251215135213W6BXN-3>BEACON,qAR,KJ6HUP:;147.030+x3732.15N/12003.80Wr147.030MHz T100 + R60m Bullion W6BXN
20251215155214W6BXN-3>BEACON,qAR,KJ6HUP:;147.030+x3732.15N/12003.80Wr147.030MHz T100 + R60m Bullion W6BXN
20251215175214W6BXN-3>BEACON,qAR,KJ6HUP:;147.030+x3732.15N/12003.80Wr147.030MHz T100 + R60m Bullion W6BXN
20251215195214W6BXN-3>BEACON,qAR,K6YIL-1:;147.030+x3732.15N/12003.80Wr147.030MHz T100 + R60m Bullion W6BXN