APRS Packet Errors for RR3AL (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
20260209103751RR3AL>APMI01,TCPIP*,qAO,RC3C:=5528.30N/03717.74ErRepeater 145.700 MHz -0.600kHz FM/C4FM T94.8 H=60m P=50W, Admin R2AE, Troitsk, New Moscow
20260209105451RR3AL>APMI01,TCPIP*,qAO,RC3C:=5528.30N/03717.74ErRepeater 145.700 MHz -0.600kHz FM/C4FM T94.8 H=60m P=50W, Admin R2AE, Troitsk, New Moscow
20260209111151RR3AL>APMI01,TCPIP*,qAO,RC3C:=5528.30N/03717.74ErRepeater 145.700 MHz -0.600kHz FM/C4FM T94.8 H=60m P=50W, Admin R2AE, Troitsk, New Moscow
20260209112851RR3AL>APMI01,TCPIP*,qAO,RC3C:=5528.30N/03717.74ErRepeater 145.700 MHz -0.600kHz FM/C4FM T94.8 H=60m P=50W, Admin R2AE, Troitsk, New Moscow
20260209114551RR3AL>APMI01,TCPIP*,qAO,RC3C:=5528.30N/03717.74ErRepeater 145.700 MHz -0.600kHz FM/C4FM T94.8 H=60m P=50W, Admin R2AE, Troitsk, New Moscow
20260209120251RR3AL>APMI01,TCPIP*,qAO,RC3C:=5528.30N/03717.74ErRepeater 145.700 MHz -0.600kHz FM/C4FM T94.8 H=60m P=50W, Admin R2AE, Troitsk, New Moscow
20260209121951RR3AL>APMI01,TCPIP*,qAO,RC3C:=5528.30N/03717.74ErRepeater 145.700 MHz -0.600kHz FM/C4FM T94.8 H=60m P=50W, Admin R2AE, Troitsk, New Moscow
20260209123651RR3AL>APMI01,TCPIP*,qAO,RC3C:=5528.30N/03717.74ErRepeater 145.700 MHz -0.600kHz FM/C4FM T94.8 H=60m P=50W, Admin R2AE, Troitsk, New Moscow
20260209125351RR3AL>APMI01,TCPIP*,qAO,RC3C:=5528.30N/03717.74ErRepeater 145.700 MHz -0.600kHz FM/C4FM T94.8 H=60m P=50W, Admin R2AE, Troitsk, New Moscow
20260209131051RR3AL>APMI01,TCPIP*,qAO,RC3C:=5528.30N/03717.74ErRepeater 145.700 MHz -0.600kHz FM/C4FM T94.8 H=60m P=50W, Admin R2AE, Troitsk, New Moscow
20260209132751RR3AL>APMI01,TCPIP*,qAO,RC3C:=5528.30N/03717.74ErRepeater 145.700 MHz -0.600kHz FM/C4FM T94.8 H=60m P=50W, Admin R2AE, Troitsk, New Moscow
20260209134451RR3AL>APMI01,TCPIP*,qAO,RC3C:=5528.30N/03717.74ErRepeater 145.700 MHz -0.600kHz FM/C4FM T94.8 H=60m P=50W, Admin R2AE, Troitsk, New Moscow
20260209140151RR3AL>APMI01,TCPIP*,qAO,RC3C:=5528.30N/03717.74ErRepeater 145.700 MHz -0.600kHz FM/C4FM T94.8 H=60m P=50W, Admin R2AE, Troitsk, New Moscow
20260209141851RR3AL>APMI01,TCPIP*,qAO,RC3C:=5528.30N/03717.74ErRepeater 145.700 MHz -0.600kHz FM/C4FM T94.8 H=60m P=50W, Admin R2AE, Troitsk, New Moscow
20260209143551RR3AL>APMI01,TCPIP*,qAO,RC3C:=5528.30N/03717.74ErRepeater 145.700 MHz -0.600kHz FM/C4FM T94.8 H=60m P=50W, Admin R2AE, Troitsk, New Moscow
20260209145251RR3AL>APMI01,TCPIP*,qAO,RC3C:=5528.30N/03717.74ErRepeater 145.700 MHz -0.600kHz FM/C4FM T94.8 H=60m P=50W, Admin R2AE, Troitsk, New Moscow
20260209150951RR3AL>APMI01,TCPIP*,qAO,RC3C:=5528.30N/03717.74ErRepeater 145.700 MHz -0.600kHz FM/C4FM T94.8 H=60m P=50W, Admin R2AE, Troitsk, New Moscow
20260209152651RR3AL>APMI01,TCPIP*,qAO,RC3C:=5528.30N/03717.74ErRepeater 145.700 MHz -0.600kHz FM/C4FM T94.8 H=60m P=50W, Admin R2AE, Troitsk, New Moscow
20260209154351RR3AL>APMI01,TCPIP*,qAO,RC3C:=5528.30N/03717.74ErRepeater 145.700 MHz -0.600kHz FM/C4FM T94.8 H=60m P=50W, Admin R2AE, Troitsk, New Moscow
20260209160051RR3AL>APMI01,TCPIP*,qAO,RC3C:=5528.30N/03717.74ErRepeater 145.700 MHz -0.600kHz FM/C4FM T94.8 H=60m P=50W, Admin R2AE, Troitsk, New Moscow
20260209161752RR3AL>APMI01,TCPIP*,qAO,RC3C:=5528.30N/03717.74ErRepeater 145.700 MHz -0.600kHz FM/C4FM T94.8 H=60m P=50W, Admin R2AE, Troitsk, New Moscow