APRS Packet Errors for OK1FCB-1 (last 24 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
20260429164209OK1FCB-1>APRS,OK2ZAW-17*,qAO,OK1BF-10:!5015.41N/0154™þÝèå@«/·7+&n `‡ªQ;—]wF“ äë’ 4.20 V Garden T3 LoRa32 433,775 MHz DP_RSSI: -122 dBm DP_SNR: -9.50 dB
20260429204100OK1FCB-1>APRS,OK2ZAW-17*,qAO,OK1BF-10:!5015.41N/:œ G
20260429211056OK1FCB-1>APRS,OK2ZAW-17*,qAO,OK1BF-10:!5015.41N/01549.34E_.../,&t˜34h46b›0:ž= BAT 4.18 V Garden T3 LoRa32 433,77`K DP_RSSI: -120 dBm DP_SNR: -0.25 dB
20260429215547OK1FCB-1>APRS,OK2ZAW-17*,qAO,OK1BF-10:!5015.t5N+01549.34E_.../...t033h50b10347 BAT 4.18 V Garden T3 LoRa32 433,775 MHz DP_RSSI: -119 dBm DP_SNR: -1.50 dB
20260430050942OK1FCB-1>APRS,OK2ZAW-17*,qAO,OK1KKY-17:!501•.41î…™53.34E_.../...t040h53b10360 BAT 4.18 V Garden T3 LoRa32 433,775 MHz DP_RSÃI: -1±±(dBm DP_SNR: -0.50 dB
20260430080931OK1FCB-1>APRS,OK2ZAW-17*,qAO,OK0BAF-10:!5015.41N/r150YHS2E_..,/..t¶¤h“3`10359 BAT 4.18 V Garden T3 LoRa32 433,775 MHz DP_RSSI: -123 dBm DP_SNR: -9.50 dB