APRS Packet Errors for UB3APB-W3 (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
20251208085225	UB3APB-W3>APRS,TCPIP*,qAU,T2SPAIN:!5516.45N/03742.67E_.../...g...t034r...p...P...hNaNbNaNStolbischevo WX 1°C
20251208085734	UB3APB-W3>APRS,TCPIP*,qAU,T2CSNGRAD:!5516.45N/03742.67E_.../...g...t034r...p...P...hNaNbNaNStolbischevo WX 1°C
20251208090242	UB3APB-W3>APRS,TCPIP*,qAU,T2CHILE:!5516.45N/03742.67E_.../...g...t034r...p...P...hNaNbNaNStolbischevo WX 1°C
20251208090743	UB3APB-W3>APRS,TCPIP*,qAU,T2SYDNEY:!5516.45N/03742.67E_.../...g...t034r...p...P...hNaNbNaNStolbischevo WX 1°C
20251208091410	UB3APB-W3>APRS,TCPIP*,qAU,T2CHILE:!5516.45N/03742.67E_.../...g...t034r...p...P...hNaNbNaNStolbischevo WX 1°C
20251208101704	UB3APB-W3>APRS,TCPIP*,qAU,T2BC:!5516.45N/03742.67E_.../...g...t034r...p...P...hNaNbNaNStolbischevo WX 1°C
20251208102212	UB3APB-W3>APRS,TCPIP*,qAU,T2SYDNEY:!5516.45N/03742.67E_.../...g...t033r...p...P...hNaNbNaNStolbischevo WX 1°C
20251208102719	UB3APB-W3>APRS,TCPIP*,qAU,T2SPAIN:!5516.45N/03742.67E_.../...g...t033r...p...P...hNaNbNaNStolbischevo WX 1°C
20251208103225	UB3APB-W3>APRS,TCPIP*,qAU,T2PERTH:!5516.45N/03742.67E_.../...g...t033r...p...P...hNaNbNaNStolbischevo WX 1°C
20251208113406	UB3APB-W3>APRS,TCPIP*,qAU,T2TAS:!5516.45N/03742.67E_.../...g...t033r...p...P...hNaNbNaNStolbischevo WX 1°C
20251208113915	UB3APB-W3>APRS,TCPIP*,qAU,T2SYDNEY:!5516.45N/03742.67E_.../...g...t033r...p...P...hNaNbNaNStolbischevo WX 1°C
20251208114425	UB3APB-W3>APRS,TCPIP*,qAU,T2SPAIN:!5516.45N/03742.67E_.../...g...t033r...p...P...hNaNbNaNStolbischevo WX 1°C
20251208114936	UB3APB-W3>APRS,TCPIP*,qAU,T2SPAIN:!5516.45N/03742.67E_.../...g...t033r...p...P...hNaNbNaNStolbischevo WX 1°C
20251208125105	UB3APB-W3>APRS,TCPIP*,qAU,T2SPAIN:!5516.45N/03742.67E_.../...g...t033r...p...P...hNaNbNaNStolbischevo WX 1°C
20251208125607	UB3APB-W3>APRS,TCPIP*,qAU,T2UKRAINE:!5516.45N/03742.67E_.../...g...t033r...p...P...hNaNbNaNStolbischevo WX 1°C
20251208130116	UB3APB-W3>APRS,TCPIP*,qAU,T2CHILE:!5516.45N/03742.67E_.../...g...t033r...p...P...hNaNbNaNStolbischevo WX 1°C
20251208130624	UB3APB-W3>APRS,TCPIP*,qAU,T2BC:!5516.45N/03742.67E_.../...g...t033r...p...P...hNaNbNaNStolbischevo WX 0°C
20251208131124	UB3APB-W3>APRS,TCPIP*,qAU,T2TAS:!5516.45N/03742.67E_.../...g...t033r...p...P...hNaNbNaNStolbischevo WX 1°C
20251208131628	UB3APB-W3>APRS,TCPIP*,qAU,T2ERFURT:!5516.45N/03742.67E_.../...g...t033r...p...P...hNaNbNaNStolbischevo WX 1°C