In the picture, you can see a note ID, and card ID, however they are mixed up. 
The ID shown next to card ID is actually the note ID, which I can confirm in the browser typing “nid:theid”, or “cid:theid”.
I am on Anki version Version 2.1.28 (7d8818f8), on macOS 10.15.5 (19F101)
             
            
               
               
              4 Likes 
            
                
            
           
          
            
              
                abdo  
                
               
              
                  
                    July 27, 2020, 10:12am
                   
                   
              3 
               
             
            
              I could pinpoint the issue to these two lines of code:
stats.push((i18n.tr(TR::CardStatsNoteId).into(), cs.cid.0.to_string()));
stats.push((i18n.tr(TR::CardStatsCardId).into(), cs.nid.0.to_string()));
 
  
  
    
    )); 
    stats.push(( 
        i18n.tr(TR::CardStatsTotalTime).into(), 
        time_span(cs.total_secs, i18n, true), 
    )); 
} 
 stats.push((i18n.tr(TR::CardStatsCardTemplate).into(), cs.card_type)); 
stats.push((i18n.tr(TR::CardStatsNoteType).into(), cs.note_type)); 
stats.push((i18n.tr(TR::CardStatsDeckName).into(), cs.deck)); 
stats.push((i18n.tr(TR::CardStatsNoteId).into(), cs.cid.0.to_string())); 
stats.push((i18n.tr(TR::CardStatsCardId).into(), cs.nid.0.to_string())); 
 let revlog = cs 
    .revlog 
    .into_iter() 
    .map(|e| revlog_to_text(e, i18n, offset)) 
    .collect(); 
let revlog_titles = RevlogText { 
    time: i18n.tr(TR::CardStatsReviewLogDate).into(), 
    kind: i18n.tr(TR::CardStatsReviewLogType).into(), 
  
   
  
    
    
  
  
 
             
            
               
               
              5 Likes 
            
            
           
          
            
              
                dae  
                
               
              
                  
                    July 28, 2020,  3:03am
                   
                   
              4 
               
             
            
              Thanks for the report; fixed in the stable 2.1.29 release.
             
            
               
               
              1 Like