SectorWire
SearchRegister
MenuClose

Australian court keeps online keno operators trading during challenge

Regulation1 min read

Summary

An Australian judge allowed Lottoland, The Lottery Corporation and Annexio Australia to continue offering online keno while KenoGo’s legal challenge proceeds. The judge granted KenoGo’s unopposed request on 22 October 2026; the challenge argues that the ban conflicts with constitutional protections for interstate trade.

Justice David Hammerschlag granted KenoGo's unopposed request on 22 October 2026, allowing Lottoland, The Lottery Corporation and Annexio Australia to continue trading online keno while the case proceeds.

KenoGo is challenging the law under Section 92 of the Australian Constitution, arguing that the ban on cross-border online keno protects pubs and clubs while allowing venue-based games. Section 92 protects trade between states, and the ban applies only to online keno, leaving games available in pubs and clubs. KenoGo's lawyers said in a legal brief that supplying keno-type lotteries online would be an offence even with a state licence, while the same games could lawfully be supplied within a state at a venue.

Online and venue-based keno are distinct products, cross-border keno is uncommon, and the law is intended to safeguard people rather than pubs, the government argues.

Anticipating the ban, The Lottery Corporation recorded an A$57 million impairment against its ACT keno licence in its 2026 financial year results. KenoGo has proposed alternatives including prohibiting fast-paced keno in venues, setting spending caps and introducing self-exclusion. On 5 November, however, the company failed in an attempt to obtain documents held by advisers to the prime minister and communications minister.

End-of-day close The Lottery Corporation (TLC), AUD, to 17 November 2026
Story date2 October 202617 November 2026

Latest reported results

The Lottery Corporation ASX: TLC

Financial year ended 30 June 2026

Revenue
AUD 3.55bn
Operating income
AUD 576.6m

Request a correction

Flag an issue

Keep reading