APRS Packet Errors for DC1MBB-7 (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
20261023221345DC1MBB-7>APLC13,qAR,OE2JPO-2:!4810.21NL4qv,7(O<r=QCbóÑÝ“ƒ
20261024005804DC1MBB-7>APLC13,qAR,OE2JPO-2:!4810$6Ÿn]!""¸?5µý‰ s¤­ÁÐ’_cube
20261024034901DC1MBB-7>APLC13,qAR,OE2JPO-2:!4810.65NLea240.55E-LoRa-APR“õbe
20261024043351DC1MBB-7>APLC13,qAR,OE2JPO-2:!48Q0H6SHL01210.55E-LoZa-APRScbe
20261024050945DC1MBB-7>APLC13,qAR,OE2JPO-2:!4810(65NL0121t*quA-LoRa-APRScube
20261024060929DC1MBB-7>APLC13,qAR,OE2JPO-2:!4810.65Îȸ12!8qBä.Ä…å¯Þtù¡¼š•Ï
20261024063923DC1MBB-7>APLC13,qAR,OE2JPO-2:!4x10+65NL0121²¬µ·M-LoRa-APRScube
20261024101451DC1MBB-7>APLC13,qAR,OE2JPO-2:!4810.65^]! "¡9.55E-LoRa-APRScube
20261024105938DC1MBB-7>APLC13,qAR,OE2JPO-2:!4810.65NL0220.55E-oa-APRScube
20261024130530DC1MBB-7>APLC13,qAR,OE2JPO-2:!481,65 L01210.55E-Hoa-APRScube
20261024154113DC1MBB-7>APLC13,qAR,OE2JPO-2:!48‘PŠ01DL330.55E%ÌoRa-APRóI‘ §
20261024165553DC1MBB-7>APLC13,qAR,OE2JPO-2:!4810.65^n!#211:45E+R§-MRScube
20261024215228DC1MBB-7>APLC13,qAR,OE2JPO-2:!481`.6eKL012qp UwE-æÅRk-APRScubÅ