APRS Packet Errors for EI4HAB-10 (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
20260208163712	EI4HAB-10>APDW17,TCPIP*,qAC,T2SJC:!5216.88NR00942.02W&144.800MHz IGate \| RPi \| RTL-SDR
20260208170712	EI4HAB-10>APDW17,TCPIP*,qAC,T2SJC:!5216.88NR00942.02W&144.800MHz IGate \| RPi \| RTL-SDR
20260208173712	EI4HAB-10>APDW17,TCPIP*,qAC,T2SJC:!5216.88NR00942.02W&144.800MHz IGate \| RPi \| RTL-SDR
20260208180712	EI4HAB-10>APDW17,TCPIP*,qAC,T2SJC:!5216.88NR00942.02W&144.800MHz IGate \| RPi \| RTL-SDR
20260208183712	EI4HAB-10>APDW17,TCPIP*,qAC,T2SJC:!5216.88NR00942.02W&144.800MHz IGate \| RPi \| RTL-SDR
20260208190712	EI4HAB-10>APDW17,TCPIP*,qAC,T2SJC:!5216.88NR00942.02W&144.800MHz IGate \| RPi \| RTL-SDR
20260208193712	EI4HAB-10>APDW17,TCPIP*,qAC,T2SJC:!5216.88NR00942.02W&144.800MHz IGate \| RPi \| RTL-SDR
20260208200712	EI4HAB-10>APDW17,TCPIP*,qAC,T2SJC:!5216.88NR00942.02W&144.800MHz IGate \| RPi \| RTL-SDR
20260208203712	EI4HAB-10>APDW17,TCPIP*,qAC,T2SJC:!5216.88NR00942.02W&144.800MHz IGate \| RPi \| RTL-SDR
20260208210712	EI4HAB-10>APDW17,TCPIP*,qAC,T2SJC:!5216.88NR00942.02W&144.800MHz IGate \| RPi \| RTL-SDR
20260208213712	EI4HAB-10>APDW17,TCPIP*,qAC,T2SJC:!5216.88NR00942.02W&144.800MHz IGate \| RPi \| RTL-SDR
20260208220712	EI4HAB-10>APDW17,TCPIP*,qAC,T2SJC:!5216.88NR00942.02W&144.800MHz IGate \| RPi \| RTL-SDR