APRS Packet Errors for N7JP (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
20260209104405N7JP>APN000,TCPIP*,qAC,T2FINLAND:@091044z4759.51N/12232.02W_200/002g009t043r000p000P000b10175h91eMB63
20260209105906N7JP>APN000,TCPIP*,qAC,T2FINLAND:@091059z4759.51N/12232.02W_222/002g006t043r000p000P000b10176h91eMB63
20260209111409N7JP>APN000,TCPIP*,qAC,T2TAS:@091114z4759.51N/12232.02W_173/002g007t043r000p000P000b10176h91eMB63
20260209112933N7JP>APN000,TCPIP*,qAC,T2UKRAINE:@091129z4759.51N/12232.02W_196/003g010t043r000p000P000b10178h91eMB63
20260209114432N7JP>APN000,TCPIP*,qAC,T2POLNW:@091144z4759.51N/12232.02W_204/003g008t043r000p000P000b10179h91eMB63
20260209115932N7JP>APN000,TCPIP*,qAC,T2CHILE:@091159z4759.51N/12232.02W_168/002g009t043r000p000P000b10180h91eMB63
20260209121438N7JP>APN000,TCPIP*,qAC,T2CHILE:@091214z4759.51N/12232.02W_176/002g010t043r000p000P000b10182h91eMB63
20260209123001N7JP>APN000,TCPIP*,qAC,T2TAS:@091229z4759.51N/12232.02W_167/003g008t042r000p000P000b10183h91eMB63
20260209124507N7JP>APN000,TCPIP*,qAC,T2SYDNEY:@091245z4759.51N/12232.02W_151/001g007t042r000p000P000b10183h91eMB63
20260209130030N7JP>APN000,TCPIP*,qAC,T2PANAMA:@091300z4759.51N/12232.02W_126/002g007t043r000p000P000b10184h91eMB63
20260209131530N7JP>APN000,TCPIP*,qAC,T2UKRAINE:@091315z4759.51N/12232.02W_123/003g008t043r000p000P000b10183h91eMB63
20260209133053N7JP>APN000,TCPIP*,qAC,T2SYDNEY:@091330z4759.51N/12232.02W_136/003g010t043r000p000P000b10184h91eMB63
20260209134605N7JP>APN000,TCPIP*,qAC,T2CSNGRAD:@091346z4759.51N/12232.02W_147/003g009t043r000p000P000b10184h89eMB63
20260209140112N7JP>APN000,TCPIP*,qAC,T2CSNGRAD:@091401z4759.51N/12232.02W_134/002g007t043r000p000P000b10186h88eMB63
20260209141613N7JP>APN000,TCPIP*,qAC,T2UKRAINE:@091416z4759.51N/12232.02W_123/003g009t043r000p000P000b10186h88eMB63
20260209143113N7JP>APN000,TCPIP*,qAC,T2UKRAINE:@091431z4759.51N/12232.02W_187/004g010t043r000p000P000b10187h88eMB63
20260209144613N7JP>APN000,TCPIP*,qAC,T2PANAMA:@091446z4759.51N/12232.02W_164/002g010t042r000p000P000b10188h88eMB63
20260209150117N7JP>APN000,TCPIP*,qAC,T2PERTH:@091501z4759.51N/12232.02W_214/002g009t...r000p000P000b10189h..eMB63
20260209151617N7JP>APN000,TCPIP*,qAC,T2ERFURT:@091516z4759.51N/12232.02W_132/003g012t...r000p000P000b10190h..eMB63
20260209153119N7JP>APN000,TCPIP*,qAC,T2FINLAND:@091531z4759.51N/12232.02W_189/001g009t...r000p000P000b10191h..eMB63
20260209154622N7JP>APN000,TCPIP*,qAC,T2UKRAINE:@091546z4759.51N/12232.02W_162/003g010t...r000p000P000b10193h..eMB63
20260209160124N7JP>APN000,TCPIP*,qAC,T2ROMANIA:@091601z4759.51N/12232.02W_206/002g009t...r...p000P000b10195h..eMB63
20260209161652N7JP>APN000,TCPIP*,qAC,T2UKRAINE:@091616z4759.51N/12232.02W_248/003g010t043r000p000P000b10195h92eMB63