ArgentinaBruno Duarte – Argentina | World Cup 2026 Player Profile

    Bruno Duarte
    Bruno Duarte
    Bruno Ezequiel Duarte
    Date of BirthJune 20, 1995 (age 31)
    Place of BirthFederal, Argentina
    Height / Weight190 / —
    PositionDefender
    Current ClubUTC Cajamarca
    34
    Career
    Appearances
    2
    Career
    Goals
    2025-26 Season
    CompetitionMPGlsAst
    Primera División1620
    Primera Nacional900
    Liga Pro900
    All Competitions3420
    0
    Int'l
    Caps
    0
    Int'l
    Goals
    Argentina's group: Group J →
    Argentina International
    VeloBet

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

    Accepts:
    Ξ
    Ł
    · 18+ · PLAY RESPONSIBLY

    World Cup 2026

    Group J →
    #TeamPWDLGDPts
    1ArgentinaArgentina220056
    2AustriaAustria210103
    3AlgeriaAlgeria2101-23
    4JordanJordan2002-30

    2026 tournament outlook

    Bruno Duarte will represent Argentina at the 2026 FIFA World Cup. Argentina have been drawn in Group J alongside Algeria, Austria, Jordan. Their campaign begins on 2026-06-16 against Algeria at Arrowhead Stadium, Kansas City. As a defender, Duarte will be looking to make an impact on the biggest stage in world football. Argentina is a 3-time World Cup champion and will be looking to add to their legacy.

    Argentina at the 2026 World Cup

    Bruno Duarte is part of the Argentina squad for the 2026 World Cup, managed by Lionel Scaloni, alongside W. Benítez, M. Acuña, V. Barco, and N. Paz among the key players.

    View full Argentina team profile →

    Related players

    Argentina Teammates

    PlayerPosition
    W. BenítezGoalkeeper
    M. AcuñaDefender
    V. BarcoMidfielder
    N. PazAttacker

    Similar Players to Watch

    PlayerCountryWhy
    A. ModibaSouth Africa South AfricaAerial presence
    Lucas MendesQatar QatarBall-playing defender
    N. AguerdMorocco MoroccoPace and recovery

    Frequently asked questions

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