APRS Packet Errors for SV4FHR-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
20251223165055SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@231650z/:L1pT/t)_2!bg002t052r000p000P000h92b10153Larissa Weather Report {UIV32N}
20251223165555SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@231655z/:L1pT/t)_2!bg002t052r000p000P000h91b10152Larissa Weather Report {UIV32N}
20251223170055SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@231700z/:L1pT/t)_2!bg002t052r000p000P000h91b10150Larissa Weather Report {UIV32N}
20251223170555SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@231705z/:L1pT/t)_2)bg002t052r000p000P000h91b10150Larissa Weather Report {UIV32N}
20251223171055SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@231710z/:L1pT/t)_2!bg002t052r000p000P000h91b10149Larissa Weather Report {UIV32N}
20251223171555SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@231715z/:L1pT/t)_2!bg002t052r000p000P000h91b10149Larissa Weather Report {UIV32N}
20251223172055SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@231720z/:L1pT/t)_2!bg002t052r000p000P000h91b10148Larissa Weather Report {UIV32N}
20251223172554SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@231725z/:L1pT/t)_2!bg002t052r000p000P000h91b10148Larissa Weather Report {UIV32N}
20251223173054SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@231730z/:L1pT/t)_2!bg002t052r000p000P000h91b10150Larissa Weather Report {UIV32N}
20251223173554SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@231735z/:L1pT/t)_-!bg002t052r000p000P000h92b10151Larissa Weather Report {UIV32N}
20251223174054SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@231740z/:L1pT/t)_,!bg002t052r000p000P000h92b10150Larissa Weather Report {UIV32N}
20251223174555SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@231745z/:L1pT/t)_,!bg002t052r000p000P000h92b10150Larissa Weather Report {UIV32N}
20251223175055SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@231750z/:L1pT/t)_,!bg002t052r000p000P000h92b10151Larissa Weather Report {UIV32N}
20251223175555SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@231755z/:L1pT/t)_,!bg002t052r000p000P000h92b10152Larissa Weather Report {UIV32N}
20251223180056SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@231800z/:L1pT/t)_,!bg002t052r000p000P000h92b10150Larissa Weather Report {UIV32N}
20251223180556SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@231805z/:L1pT/t)_,!bg002t052r000p000P000h92b10149Larissa Weather Report {UIV32N}
20251223181056SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@231810z/:L1pT/t)_,!bg002t051r000p000P000h93b10152Larissa Weather Report {UIV32N}
20251223181556SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@231815z/:L1pT/t)_,!bg002t051r000p000P000h93b10152Larissa Weather Report {UIV32N}