APRS Packet Errors for OK1UOJ (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
20251214144024OK1UOJ>APRS,OK2ZAW-17*,qAS,OE3APM-11:!4957.90N/0539E_135/002g003t036h100b10305_BATT=3.97V DP_RSSI: -118 dBm DP_SNR: 2.50 dB
20251214145852OK1UOJ>APRS,OK2ZAW-17*,qAS,OE3XRC-11:!4913.=0N/0:0539E_138/003g003t036h100b10303_BATT=3.97V DP_RSSI: -119 dBm DP_SNR: 2.75 dB
20251214153544OK1UOJ>APRS,OK2ZAW-17*,qAO,OK2AF-10:!4957.90NO01.39E_116/001g002t036h100b10303_rBTb[._)DR]pSSI: -118 dBm DP_SNR: 2.25 dB
20251214155850OK1UOJ>APRS,OK2ZAW-17*,qAO,OK2AF-10:!4957.90N/005.39E_13
20251214155854OK1UOJ>APRS,OK2ZAW-17*,qAS,OE3APM-11:!4957./00?"39E_134/001g002t036h3bT9302_rAWTP._1V&DP_RSSI: -118 dBm DP_SNR: 2.75 dB
20251214164023OK1UOJ>APRS,OK2ZAW-17*,qAO,OE3XOC-11:!4957.9|+t68.;9E_117/002g003t036h100b10238_BATT=3.95VDR_SI: 1Q dBm DP_SNR: 2.75 dB
20251214171243OK1UOJ>APRS,OK2ZAW-17*,qAO,OK1BF-10:!4957.90N/01MsN2_
20251214171243OK1UOJ>APRS,OK2ZAW-17*,qAO,OK2AF-10:!4957.9 O.10605.39Fo200;g003t036h10B0296_BATT=3.95V DP_RSSI: -118 dBm DP_SNR: 2.50 dB
20251214173111OK1UOJ>APRS,OK2ZAW-17*,qAO,OE3XOC-11:!4957.90N/01605.3EW9R6Z7g84tr,00bB]4:.95V DP_RSSI: -118 &
20251214180808OK1UOJ>APRS,OK2ZAW-17*,qAO,OK0BAF-10:!4957.90N/01605.39E_1Co0`S03h1 b29?d+< dB
20251214180808OK1UOJ>APRS,OK2ZAW-17*,qAO,OK1BF-10:!4957.90N/01605.39E_1ffء fx宷Sg%+(l,}v#2ֵG,Hȕ~>!TS