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
20210419214356SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@192143z/:L1pT/t)_Y)bg003t051r000p000P000h66b10100larissa weather report {UIV32N}
20210419214901SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@192148z/:L1pT/t)_S)bg003t051r000p000P000h66b10100larissa weather report {UIV32N}
20210419215711SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@192153z/:L1pT/t)_Y)bg002t050r000p000P000h67b10098larissa weather report {UIV32N}
20210419215856SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@192158z/:L1pT/t)__)bg002t050r000p000P000h67b10098larissa weather report {UIV32N}
20210419220358SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@192203z/:L1pT/t)_I2bg003t050r000p000P000h69b10100larissa weather report {UIV32N}
20210419220856SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@192208z/:L1pT/t)_I2bg005t048r000p000P000h72b10099larissa weather report {UIV32N}
20210419221400SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@192213z/:L1pT/t)_C2bg003t048r000p000P000h73b10099larissa weather report {UIV32N}
20210419221945SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@192218z/:L1pT/t)_C2bg006t047r000p000P000h74b10098larissa weather report {UIV32N}