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
20260309170120	SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@091701z/:L1pT/t)_72bg009t050r000p000P000h59b10258Larissa Weather Report {UIV32N}
20260309170620	SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@091706z/:L1pT/t)_72bg009t050r000p000P000h59b10260Larissa Weather Report {UIV32N}
20260309171119	SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@091711z/:L1pT/t)_72bg009t049r000p000P000h60b10260Larissa Weather Report {UIV32N}
20260309180118	SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@091801z/:L1pT/t)_7)bg009t047r000p000P000h66b10264Larissa Weather Report {UIV32N}
20260309180618	SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@091806z/:L1pT/t)_7)bg009t047r000p000P000h67b10264Larissa Weather Report {UIV32N}
20260309181119	SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@091811z/:L1pT/t)_2!bg009t047r000p000P000h68b10263Larissa Weather Report {UIV32N}
20260309181619	SV4FHR-2>APU25N,TCPIP*,qAS,SV4FHR-1:@091816z/:L1pT/t)_72bg009t047r000p000P000h73b10264Larissa Weather Report {UIV32N}