APRS Packet Errors for LZ4NY-T (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
20260722172024LZ4NY-T>APM2A0,TCPIP*,qAS,MeshGW:!0000.00NM00000.00Ea/A=000000 Hw:TRACKER_T1000_E RSSI:-102 SNR:4.5 Bat:3.96v BatLvl:80% Air:0.095% Utl:11.227% Up:1h35m11s
20260722172100LZ4NY-T>APM2A0,TCPIP*,qAS,MeshGW:!0000.00NM00000.00Ea/A=000000 Hw:TRACKER_T1000_E RSSI:-101 SNR:4.5 Bat:3.94v BatLvl:78% Air:0.016% Utl:6.408% Up:3h6m15s
20260722185326LZ4NY-T>APM2A0,TCPIP*,qAS,MeshGW:!0000.00NM00000.00Ea/A=000000 Hw:TRACKER_T1000_E RSSI:-111 SNR:-0.75 Bat:3.94v BatLvl:78% Air:0.016% Utl:6.408% Up:3h6m15s
20260722185400LZ4NY-T>APM2A0,TCPIP*,qAS,MeshGW:!0000.00NM00000.00Ea/A=000000 Hw:TRACKER_T1000_E RSSI:-112 SNR:-1.75 Bat:3.92v BatLvl:74% Air:0.038% Utl:1.863% Up:4h39m16s
20260722204800LZ4NY-T>APM2A0,TCPIP*,qAS,MeshGW:!0000.00NM00000.00Ea/A=000000 Hw:TRACKER_T1000_E RSSI:-34 SNR:6.75 Bat:3.91v BatLvl:73% Air:0.034% Utl:5.34% Up:5h59m16s
20260722215325LZ4NY-T>APM2A0,TCPIP*,qAS,MeshGW:!0000.00NM00000.00Ea/A=000000 Hw:TRACKER_T1000_E RSSI:-37 SNR:6.5 Bat:3.91v BatLvl:73% Air:0.034% Utl:5.34% Up:5h59m16s
20260722215400LZ4NY-T>APM2A0,TCPIP*,qAS,MeshGW:!0000.00NM00000.00Ea/A=000000 Hw:TRACKER_T1000_E RSSI:-35 SNR:6.25 Bat:3.88v BatLvl:69% Air:0.032% Utl:3.727% Up:7h39m17s