APRS Packet Errors for DM2PF (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
20260208152847ON6ZQ>APN100,TCPIP*,qAC,SIXTH:;DM2PF *081528z4818.91NS00907.39E;007.037MHz SOTA activation DM/BW-852
20260208154242ON6ZQ>APN100,TCPIP*,qAC,FOURTH:;DM2PF *081542z4818.91NS00907.39E;007.037MHz SOTA activation DM/BW-852
20260208154739ON6ZQ>APN100,TCPIP*,qAC,THIRD:;DM2PF *081547z4818.91NS00907.39E;007.037MHz SOTA activation DM/BW-852
20260208155748ON6ZQ>APN100,TCPIP*,qAC,FOURTH:;DM2PF *081557z4818.91NS00907.39E;007.037MHz SOTA activation DM/BW-852
20260208161127ON6ZQ>APN100,TCPIP*,qAC,FIRST:;DM2PF *081611z4818.91NS00907.39E;007.100MHz SOTA activation DM/BW-852
20260208162209ON6ZQ>APN100,TCPIP*,qAC,NINTH:;DM2PF *081622z4818.91NS00907.39E;014.039MHz SOTA activation DM/BW-852
20260208163529ON6ZQ>APN100,TCPIP*,qAC,FIFTH:;DM2PF *081635z4818.91NS00907.39E;010.120MHz SOTA activation DM/BW-852