UruguayFacundo Pellistri – Uruguay | World Cup 2026 Player Profile

    Facundo Pellistri
    Facundo Pellistri
    Facundo Pellistri Rebollo
    Date of BirthDecember 20, 2001 (age 24)
    Place of BirthMontevideo, Uruguay
    Height / Weight175 / 69
    PositionForward
    Current ClubPanathinaikos
    52
    Career
    Appearances
    4
    Career
    Goals
    2025-26 Season
    CompetitionMPGlsAst
    World Cup - Qualification South America1702
    Friendlies200
    UEFA Europa League600
    Super League 1802
    UEFA Champions League200
    Cup410
    UEFA Europa Conference League720
    Copa America611
    All Competitions5245
    38
    Int'l
    Caps
    3
    Int'l
    Goals
    Uruguay's group: Group H →
    Uruguay International
    VeloBet

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

    Accepts:
    Ξ
    Ł
    · 18+ · PLAY RESPONSIBLY

    World Cup 2026

    Group H →
    #TeamPWDLGDPts
    1SpainSpain321057
    2Cabo VerdeCabo Verde303003
    3UruguayUruguay3021-12
    4Saudi ArabiaSaudi Arabia3021-42

    2026 tournament outlook

    Facundo Pellistri will represent Uruguay at the 2026 FIFA World Cup. Uruguay have been drawn in Group H alongside Spain, Saudi Arabia, Cabo Verde. Their campaign begins on 2026-06-15 against Saudi Arabia at Hard Rock Stadium, Miami. As a forward, Pellistri will be looking to make an impact on the biggest stage in world football. Uruguay is a 2-time World Cup champion and will be looking to add to their legacy.

    Uruguay at the 2026 World Cup

    Facundo Pellistri is part of the Uruguay squad for the 2026 World Cup, managed by Marcelo Bielsa, alongside S. Mele, J. Giménez, P. Alcoba, and G. de Arrascaeta among the key players.

    View full Uruguay team profile →

    Related players

    Uruguay Teammates

    PlayerPosition
    S. MeleGoalkeeper
    J. GiménezDefender
    P. AlcobaMidfielder
    G. de ArrascaetaAttacker

    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.