Skip to content

Tours & Events

BLACKPINK's LISA Opens 'VIVA LA LISA' Las Vegas Residency at Caesars Palace on Nov. 12

LISA's six-show 'VIVA LA LISA' residency at The Colosseum at Caesars Palace begins on Thursday, Nov. 12, with shows on Nov. 12-14 and Nov. 27-29, according to Caesars Entertainment.

By 2FC NEWSROOM · Published

Official 'Viva La Lisa' poster for The Colosseum at Caesars Palace listing the November dates
Image: Caesars Entertainment

LISA's Las Vegas run starts this week. The BLACKPINK member opens 'VIVA LA LISA' at The Colosseum at Caesars Palace on Thursday, Nov. 12, the first of six shows across two weekends.

The residency was first announced with four dates, Nov. 13-14 and Nov. 27-28. Caesars Entertainment said those shows sold out in under 10 minutes and added Nov. 12 and Nov. 29, bringing the total to six. Caesars bills the run as the first Las Vegas residency by a K-pop artist.

The shows come weeks after LISA released her solo EP 'PRESS PLAY' on Oct. 23, which debuted at No. 35 on the Billboard 200. The second set of dates runs Nov. 27-29.

Confirmed

  • Caesars Entertainment lists six 'VIVA LA LISA' shows at The Colosseum at Caesars Palace: Nov. 12, 13, 14, 27, 28 and 29, 2026.
  • In its Sept. 29 press release, Caesars said the first four dates sold out in under 10 minutes and that it added Nov. 12 and Nov. 29 due to demand.
  • Caesars describes the run as making LISA the first K-pop artist with a Las Vegas residency.

Reported by other outlets

  • Top Star News reports the residency follows LISA's solo EP 'PRESS PLAY,' released Oct. 23 with tracks including 'Tarantino' and 'SaWaDiKa.'

Unconfirmed

  • The setlist and production details for the shows have not been announced.

Analysis

Interpretation by 2FC NEWSROOM, not reported fact.

2FC NEWSROOM analysis: The 4,300-seat Colosseum is far smaller than the stadiums BLACKPINK plays, so the residency gives LISA a format closer to a Vegas show than a K-pop tour stop.

Conflicts of interest: None.

Follow @2fastcloud on X

Spot an error? See our corrections policy.