APRS Packet Errors for PE1PKB-2 (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
20260209102859PE1PKB-2>APRS,qAR,PE1PKB-10:!5215.61N/00536.71E[Pieter, MTP3250 APRS-TETRA
20260209105859PE1PKB-2>APRS,qAR,PE1PKB-10:!5215.61N/00536.70E[Pieter, MTP3250 APRS-TETRA
20260209112859PE1PKB-2>APRS,qAR,PE1PKB-10:!5215.61N/00536.70E[Pieter, MTP3250 APRS-TETRA
20260209115859PE1PKB-2>APRS,qAR,PE1PKB-10:!5215.61N/00536.70E[Pieter, MTP3250 APRS-TETRA
20260209122859PE1PKB-2>APRS,qAR,PE1PKB-10:!5215.61N/00536.70E[Pieter, MTP3250 APRS-TETRA
20260209125859PE1PKB-2>APRS,qAR,PE1PKB-10:!5215.61N/00536.70E[Pieter, MTP3250 APRS-TETRA
20260209132859PE1PKB-2>APRS,qAR,PE1PKB-10:!5215.61N/00536.71E[Pieter, MTP3250 APRS-TETRA
20260209135859PE1PKB-2>APRS,qAR,PE1PKB-10:!5215.61N/00536.70E[Pieter, MTP3250 APRS-TETRA
20260209142859PE1PKB-2>APRS,qAR,PE1PKB-10:!5215.61N/00536.70E[Pieter, MTP3250 APRS-TETRA
20260209145859PE1PKB-2>APRS,qAR,PE1PKB-10:!5215.61N/00536.70E[Pieter, MTP3250 APRS-TETRA
20260209152859PE1PKB-2>APRS,qAR,PE1PKB-10:!5215.61N/00536.71E[Pieter, MTP3250 APRS-TETRA
20260209155859PE1PKB-2>APRS,qAR,PE1PKB-10:!5215.61N/00536.70E[Pieter, MTP3250 APRS-TETRA