APRS Packet Errors for IV3SCP-1 (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
20260209133001IV3SCP-1>APRS,TCPIP*,qAC,T2PRT:@133001z4548.90N/01327.00E%/A=000027 DXCluster 44.31.102.250 7300
20260209140001IV3SCP-1>APRS,TCPIP*,qAC,T2UKRAINE:@140001z4548.90N/01327.00E%/A=000027 DXCluster 44.31.102.250 7300
20260209143002IV3SCP-1>APRS,TCPIP*,qAC,T2CSNGRAD:@143001z4548.90N/01327.00E%/A=000027 DXCluster 44.31.102.250 7300
20260209150002IV3SCP-1>APRS,TCPIP*,qAC,T2UKRAINE:@150001z4548.90N/01327.00E%/A=000027 DXCluster 44.31.102.250 7300
20260209153001IV3SCP-1>APRS,TCPIP*,qAC,T2SPAIN:@153001z4548.90N/01327.00E%/A=000027 DXCluster 44.31.102.250 7300
20260209160002IV3SCP-1>APRS,TCPIP*,qAC,T2UKRAINE:@160002z4548.90N/01327.00E%/A=000027 DXCluster 44.31.102.250 7300
20260209163002IV3SCP-1>APRS,TCPIP*,qAC,T2ROMANIA:@163001z4548.90N/01327.00E%/A=000027 DXCluster 44.31.102.250 7300
20260209173001IV3SCP-1>APRS,TCPIP*,qAC,T2ROMANIA:@173001z4548.90N/01327.00E%/A=000027 DXCluster 44.31.102.250 7300
20260209180002IV3SCP-1>APRS,TCPIP*,qAC,T2UKRAINE:@180002z4548.90N/01327.00E%/A=000027 DXCluster 44.31.102.250 7300
20260209190002IV3SCP-1>APRS,TCPIP*,qAC,T2ERFURT:@190002z4548.90N/01327.00E%/A=000027 DXCluster 44.31.102.250 7300