APRS Packet Errors for WB7AAV (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
20261002192342WB7AAV>APRS,TCP,qAS,AE7AF:@923z3922.13N/10455.48W_172/009g018t071r000p0000h37eMB6SKMI0PIPS,N39,04,000,000
20261002193541WB7AAV>APRS,TCPIP*,qAS,AE7AF:@021922.13N455.48W_150/1t072rp000P000b10238eMB3
20261002201348WB7AAV>RS,TCPIP*,qAS,AE7AF:@022013.13N/10455.413/011g021t0700p0000b10241eMB36
20261002201549WB7AAV>APRIAMA,qAR,AE7AF:@0015z3922.055.48_071r000p010240h41eMB3
20261002221016WB7AAV>APRS,TCPIP*,qAS,AE7AF:@022210z392155.48W_186/013g025t070r000p000h40eMB