APRS Packet Errors for DX1PAR-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
20260812110011DX1PAR-9>APBPQ1,TCPIP*,qAC,T2OSAKA:!14.6040NW121.0124E/BBS & RMS Manila
20260812110511DX1PAR-9>APBPQ1,TCPIP*,qAC,T2OSAKA:!14.6040NW121.0124E/BBS & RMS Manila
20260812111011DX1PAR-9>APBPQ1,TCPIP*,qAC,T2OSAKA:!14.6040NW121.0124E/BBS & RMS Manila
20260812111511DX1PAR-9>APBPQ1,TCPIP*,qAC,T2OSAKA:!14.6040NW121.0124E/BBS & RMS Manila
20260812112011DX1PAR-9>APBPQ1,TCPIP*,qAC,T2OSAKA:!14.6040NW121.0124E/BBS & RMS Manila
20260812112511DX1PAR-9>APBPQ1,TCPIP*,qAC,T2OSAKA:!14.6040NW121.0124E/BBS & RMS Manila
20260812113011DX1PAR-9>APBPQ1,TCPIP*,qAC,T2OSAKA:!14.6040NW121.0124E/BBS & RMS Manila
20260812113511DX1PAR-9>APBPQ1,TCPIP*,qAC,T2OSAKA:!14.6040NW121.0124E/BBS & RMS Manila
20260812114011DX1PAR-9>APBPQ1,TCPIP*,qAC,T2OSAKA:!14.6040NW121.0124E/BBS & RMS Manila
20260812114511DX1PAR-9>APBPQ1,TCPIP*,qAC,T2OSAKA:!14.6040NW121.0124E/BBS & RMS Manila
20260812115011DX1PAR-9>APBPQ1,TCPIP*,qAC,T2OSAKA:!14.6040NW121.0124E/BBS & RMS Manila
20260812115511DX1PAR-9>APBPQ1,TCPIP*,qAC,T2OSAKA:!14.6040NW121.0124E/BBS & RMS Manila
20260812120011DX1PAR-9>APBPQ1,TCPIP*,qAC,T2OSAKA:!14.6040NW121.0124E/BBS & RMS Manila