AustriaMichael Gregoritsch – Austria | World Cup 2026 Player Profile

    Michael Gregoritsch
    Michael Gregoritsch
    Date of BirthApril 18, 1994 (age 32)
    Place of BirthGraz, Austria
    Height / Weight193 / 91
    PositionForward
    Current ClubBrondby
    73
    Career
    Appearances
    21
    Career
    Goals
    2025-26 Season
    CompetitionMPGlsAst
    Friendlies311
    World Cup100
    Superliga1121
    Bundesliga1762
    UEFA Europa Conference League110
    Bundesliga2021
    DFB Pokal310
    Euro Championship410
    UEFA Nations League530
    World Cup - Qualification Europe840
    All Competitions73215
    22
    Int'l
    Caps
    10
    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

    Michael Gregoritsch 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 forward, Gregoritsch 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

    Michael Gregoritsch 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

    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.