APRS Packet Errors for ZS6SJC-15 (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
20260208135507ZS6SJC-15>APCDS0,TCPIP*,qAC,T2SPAIN:@135505h2539.69S/02810.44E>010/000/A=004083 SATS10 -71.0dBm
20260208144124ZS6SJC-15>APCDS0,TCPIP*,qAC,T2POLC:@144121h2539.69S/02810.44E>010/000/A=004077 SATS10 -73.0dBm
20260208152739ZS6SJC-15>APCDS0,TCPIP*,qAC,T2CZECH:@152737h2539.69S/02810.44E>010/000/A=004082 SATS09 -71.0dBm
20260208161356ZS6SJC-15>APCDS0,TCPIP*,qAC,T2FINLAND:@161354h2539.69S/02810.44E>010/000/A=004075 SATS08 -75.0dBm
20260208170010ZS6SJC-15>APCDS0,TCPIP*,qAC,T2DENMARK:@170008h2539.69S/02810.44E>010/000/A=004077 SATS09 -73.0dBm
20260208174626ZS6SJC-15>APCDS0,TCPIP*,qAC,T2CZECH:@174624h2539.69S/02810.43E>010/000/A=004080 SATS09 -73.0dBm
20260208183242ZS6SJC-15>APCDS0,TCPIP*,qAC,T2CSNGRAD:@183240h2539.69S/02810.44E>010/000/A=004081 SATS10 -73.0dBm