AustriaJakob Odehnal – Austria | World Cup 2026 Player Profile

    Jakob Odehnal
    Jakob Odehnal
    Date of BirthAugust 10, 2001 (age 24)
    Place of BirthWien, Austria
    Height / Weight195 / 80
    PositionGoalkeeper
    Current ClubUnião de Leiria
    50
    Career
    Appearances
    0
    Career
    Goals
    2025-26 Season
    CompetitionMPGlsAst
    Friendlies Clubs1500
    Segunda Liga500
    2. Liga2900
    Cup100
    All Competitions5000
    15
    Int'l
    Caps
    0
    Int'l
    Goals
    Austria's group: Group J →
    Austria 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

    Jakob Odehnal will represent Austria at the 2026 FIFA World Cup. Austria have been drawn in Group J alongside Argentina, Algeria, Jordan. Their campaign begins on 2026-06-16 against Jordan at Levi's Stadium, San Francisco. As a goalkeeper, Odehnal will be looking to make an impact on the biggest stage in world football. Austria's best World Cup finish is 3rd place (1954). They'll be aiming to go further in 2026.

    Austria at the 2026 World Cup

    Jakob Odehnal is part of the Austria squad for the 2026 World Cup, managed by Ralf Rangnick, alongside T. Lawal, D. Affengruber, C. Baumgartner, and M. Arnautović among the key players.

    View full Austria team profile →

    Related players

    Austria Teammates

    PlayerPosition
    T. LawalGoalkeeper
    D. AffengruberDefender
    C. BaumgartnerMidfielder
    M. ArnautovićAttacker

    Similar Players to Watch

    PlayerCountryWhy
    M. HarrarMorocco MoroccoShot-stopping
    Ahmed BasilIraq IraqDistribution
    Kim Dong-HeonSouth Korea South KoreaCommand of area

    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.