APRS Packet Errors for N2VEN-3 (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
20250717160431N2VEN-3>APLRT1,WIDE1-1,WIDE2-1,qAO,N2VEN-10:!/9nG9<#Rm_ {Q.../...g...t082h34b10158
20250717162616N2VEN-3>APLRT1,WIDE1-1,WIDE2-1,qAO,N2VEN-10:!/9nGT<#S,_ TQ.../...g...t081h35b10149
20250717163621N2VEN-3>APLRT1,WIDE1-1,WIDE2-1,qAO,N2VEN-10:!/9nH5<#S9_ @Q.../...g...t080h36b10144 Bat=4.19V (100%)
20250717164624N2VEN-3>APLRT1,WIDE1-1,WIDE2-1,qAO,N2VEN-10:!/9nH<#T[_ /Q.../...g...t081h36b10274
20250717165628N2VEN-3>APLRT1,WIDE1-1,WIDE2-1,qAO,N2VEN-10:!/9nI,<#Td_ 6Q.../...g...t080h37b10276
20250717183537N2VEN-3>APLRT1,WIDE1-1,WIDE2-1,qAO,N2VEN-10:!/9nHA<#SN_ eQ.../...g...t082h37b10142
20250717184541N2VEN-3>APLRT1,WIDE1-1,WIDE2-1,qAO,N2VEN-10:!/9nE^<#Se_ FQ.../...g...t082h37b10201
20250717185545N2VEN-3>APLRT1,WIDE1-1,WIDE2-1,qAO,N2VEN-10:!/9nEn<#T*_ tQ.../...g...t082h36b10217
20250717190549N2VEN-3>APLRT1,WIDE1-1,WIDE2-1,qAO,N2VEN-10:!/9nH/<#Sx_ *Q.../...g...t081h36b10146
20250717191554N2VEN-3>APLRT1,WIDE1-1,WIDE2-1,qAO,N2VEN-10:!/9nH=<#T1_ TQ.../...g...t081h36b10119