APRS Packet Errors for SR3WXA (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
20260429144545SR3WXA>APTT4,SR3NJE*,qAR,SP3TLU:@29143852E_000/000g000t37b10307L076.DsV
20260430010700SR3WXA>APTT4,SR3NJE*,qAR,SP3TLU:=5224.78N80 Poznan op. SP"46}
20260430015414SR3WXA>APTT4,SR3NJE*,qAR,SP3TLU:@300147z5224.78N/01653.
20260430022927SR3WXA>APTT4,SR3NJE*,qAR,SP3TLU:@300222035r000p000P000h
20260430031411SR3WXA>APTT4,SR3NJE*,qAR,SP3TLU:@30030752E_000/000g000t034r000p000P000hP
20260430042933SR3WXA>APTT4,SR3NJE*,qAR,SP3TLU:@30042252E_000/000g000t80b10325L047.DsVop. Michal, 73!