APRS Packet Errors for EA5JUX (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
20260208142154EA5JUX>APRS,TCPIP*,qAC,T2CHILE:@081422z3737.92N/00044.72W_315/014g024t061r000p000P000b10080h50eMH51
20260208144150EA5JUX>APRS,TCPIP*,qAC,T2PERTH:@081442z3737.92N/00044.72W_000/016g032t062r000p000P000b10082h51eMH51
20260208144651EA5JUX>APRS,TCPIP*,qAC,T2CAEAST:@081447z3737.92N/00044.72W_000/017g032t062r000p000P000b10082h51eMH51
20260208153200EA5JUX>APRS,TCPIP*,qAC,T2SPAIN:@081532z3737.92N/00044.72W_338/015g023t062r000p000P000b10088h54eMH51
20260208154700EA5JUX>APRS,TCPIP*,qAC,T2SYDNEY:@081547z3737.92N/00044.72W_338/013g025t062r000p000P000b10092h51eMH51
20260208175150EA5JUX>APRS,TCPIP*,qAC,T2TAS:@081752z3737.92N/00044.72W_293/002g009t054r000p000P000b10110h63eMH51
20260208180647EA5JUX>APRS,TCPIP*,qAC,T2ROMANIA:@081807z3737.92N/00044.72W_248/002g006t054r000p000P000b10111h64eMH51
20260208182655EA5JUX>APRS,TCPIP*,qAC,T2CHILE:@081827z3737.92N/00044.72W_225/002g007t057r000p000P000b10113h55eMH51
20260208184154EA5JUX>APRS,TCPIP*,qAC,T2TAS:@081842z3737.92N/00044.72W_248/002g007t056r000p000P000b10118h54eMH51
20260208190146EA5JUX>APRS,TCPIP*,qAC,T2SPAIN:@081902z3737.92N/00044.72W_203/002g004t056r000p000P000b10122h55eMH51