APRS Packet Errors for LU9EV-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
20170920073824LU9EV-2>APN383,WIDE2-2,qAR,LW1DXP-10:!3832.0 via WIDE2-2
20170920090201LU9EV-2>BEACON,WIDE2-2,qAR,LW1DXP-10:!3832.8907.84W#phg22304/APRS Digipiter
20170920095001LU9EV-2>BEACON,WIDE2-2,qAR,LW1DXP-10:!3832.g22304/APRS Digipiter
20170920105401LU9EV-2>APN383,WIDE2-2,qAR,LW1DXP-10:!3RS Digipiter
20170920110649LU9EV-2>APN383,WIDE2-1,qAR,LW1DXP-10:!3832.88S/0LW5DR-9>LW5DR-10>WIDE1*>WIDE2-1>SX342Y:`VHcmh2>/]"3{}=
20170920112409LU9EV-2>BEACON,WIDE2-2,qAR,LW1DXP-10:!3832.88S/DE2-2>APU25N:@201121z3832.70S/05844.20W_000/007g008t041r000p000P000h61b10067Jorge lw5dr@yahoo.com.ar
20170920120833LU9EV-2>APN383,qAR,LW1DXP-10:!3832.88S/05907.8U via WIDE2-2
20170920122147LU9EV-2>APN383,qAR,LW1DXP-10:!3832.88SEV-2*>WIDE2-2>APN383:gipiter 144.930 Mhz Radio Club Necochea