United StatesCameron Carter-Vickers – United States | World Cup 2026 Player Profile

    Cameron Carter-Vickers
    Cameron Carter-Vickers
    Cameron Robert Carter-Vickers
    Date of BirthDecember 31, 1997 (age 28)
    Place of BirthSouthend-on-Sea, England
    Height / Weight183 / 92
    PositionDefender
    Current ClubCeltic
    21
    Career
    Appearances
    1
    Career
    Goals
    2025-26 Season
    CompetitionMPGlsAst
    UEFA Europa League300
    Premiership700
    UEFA Champions League200
    FA Cup400
    League Cup310
    CONCACAF Nations League100
    Copa America100
    All Competitions2110
    5
    Int'l
    Caps
    0
    Int'l
    Goals
    United States's group: Group D →
    United States International
    VeloBet

    Get a $20 World Cup Free Bet — No Deposit Required

    Accepts:
    Ξ
    Ł
    · 18+ · PLAY RESPONSIBLY

    Cameron Carter-Vickers — latest news

    United States
    Preview

    United States vs Their Toughest Group C Rival: Cameron Carter-Vickers's Biggest World Cup Test

    March 14, 2026

    How Cameron Carter-Vickers can make a difference for United States in their most challenging group stage match at the 2026 World Cup...

    United States
    Analysis

    How Cameron Carter-Vickers Became United States's Most Important Player

    March 8, 2026

    The story of Cameron Carter-Vickers's rise to becoming a key figure in United States's World Cup campaign...

    United States
    Analysis

    Cameron Carter-Vickers's Best Season: Breaking Down Their Club Campaign

    February 20, 2026

    A detailed look at Cameron Carter-Vickers's current club form and what it means for United States's World Cup hopes...

    United States
    Preview

    World Cup 2026: Can Cameron Carter-Vickers Fire United States to Glory?

    March 1, 2026

    With the World Cup approaching, Cameron Carter-Vickers's output could be the deciding factor in United States's campaign...

    Data is sourced from API-Football and updated regularly. If you notice incorrect information, it will be corrected in the next data refresh.