Auracast Venues Tracker: Where Broadcasts Are Live

Venue tracker Case index• Checked 2026-09 Verified Last verified 2026-09-25
Quick answer

This tracker indexes documented Auracast deployments by venue class — theaters, stadiums, universities, churches, transit, airports — with the source for every entry. The Bluetooth SIG lists theatres, universities, churches, museums and stadiums among locations already deploying, and the documented cases run from Sydney's Opera House to Brighton's rail station. Entries carry check dates; deployments change, so verify with the venue before you go.

Figures on this page were checked September 2026. Deployments change; every entry carries its source and check date, and the venue’s own pages govern what is live today.

How to read this tracker

This page indexes Auracast deployments that are documented — named in a dated, checkable source such as a Bluetooth SIG venue write-up, a manufacturer announcement, or trade press. That rule keeps the list honest and also keeps it incomplete: reporting lags reality, venues go live between checks, and some of the best installations never issue a press release. Treat this as the annotated map of cases worth knowing by name, not a census.

The companion pages on this site give each venue class its own depth — airports, stadiums, theaters, museums, universities, cinemas, transit and churches — and every entry in the matrix below links to the class page where its case is documented in full.

Documented deployments

VenueClassThe documented factChecked
Frankfurt AirportAirportFirst airport worldwide streaming gate announcements; Terminal 1 gates A16/A17; QR join2026-09-23
Bristol Temple MeadsTransitFirst public integration of Auri in a transport environment; 10 transmitters, platforms 9-12 + subway + ticket hall2026-09-23
Brighton stationTransitAuri install made permanent; GTR-sponsored; announcements at no cost to passengers2026-09-23
Stadium TaranakiStadium21,000-seat arena; commentary, multi-language and assistive audio feeds2026-09-23
Sydney Opera HouseTheaterPlayhouse, Drama Theatre and Studio; adoption reported from March 20252026-09-23
Everyman Theatre (UK)TheaterInfrared ALS replaced after 20 years; seating limits eliminated2026-09-23
Marriott Theatre (IL)TheaterRegional venue deployment for accessibility and assisted listening2026-09-23
Vue CinemasCinemaAuri across 200 screens / 20 cinemas — more than 28% of circuit admissions2026-09-23
UAL Creative Computing InstituteUniversityClassroom assistive listening gap closed; clarity, stigma and futureproofing goals2026-09-23
Grace Lutheran Church (IL)ChurchDirect-to-ear streaming; no seat restrictions, no specialized devices2026-09-23
Christ Presbyterian Church (MN)ChurchAging hardware replaced; cost-effective, scalable Auracast for a large congregation2026-09-23

By venue class

Each class page on this site carries the full cases, the compliance framing and the patron checklist. The short index: theaters have the deepest documentation (four named cases); stadiums have the scale case; airports have the first-airport claim and the QR-code join; transit has the pilot-to-permanent arc; universities have the classroom-accessibility case; museums have the BYOD tour case; cinemas have the 200-screen rollout; and churches have both the add case and the replace case.

The SIG’s own expansion reporting adds the classes where documentation is still thin but direction is stated: public transportation systems generally, tourist attractions, and visitor centers. Entries graduate onto this tracker when they get sources, not when they get press releases.

Where the cases come from

Three source tiers feed this tracker, in descending order of authority. Bluetooth SIG write-ups carry the most weight — the 15-venues roundup and the per-venue blog posts are the official record, updated as the SIG adds cases. Manufacturer announcements (Ampetronic and Listen Technologies for the Auri system) document their own installations with dates and numbers. Trade press (Hearing Review, AVNation and peers) covers deployments the parties do not announce themselves; entries sourced only to trade press are marked as such on their class pages.

Two standing caveats. Venues rotate content and coverage — a deployment documented at two gates may cover a terminal by now, or a service may have paused. And the SIG’s location-profiles pages, which profile documented venues, may be temporarily unavailable during maintenance; this was observed during the September 2026 check for this page. When they are, the blog write-ups above remain checkable through their archives.

For venue operators

The pattern across every documented case: one room, one transmitter, one broadcast, the audience’s own devices as receivers — installed first where assistive listening was missing or aging, then expanded by content lane. If your venue has a PA and a power outlet in the right places, the deployment question is scheduling, not feasibility.

FAQ

The documented set tracked here spans every class on this site: Frankfurt Airport (gates A16/A17), Bristol Temple Meads and Brighton stations (transit), Stadium Taranaki (21,000 seats), the Sydney Opera House, the Everyman and Marriott theaters, the University of the Arts London's CCI, Grace Lutheran and Christ Presbyterian churches, and Vue's 200-screen cinema rollout — each with a dated source on its class page.

Wherever a venue has installed broadcast capability, which is a growing class-by-class map rather than a single switch. The documented cases tracked here already include an airport, two train stations, a 21,000-seat stadium, theaters, a university, churches and a 200-screen cinema chain, and each entry carries its dated source. The class pages linked above hold the per-venue detail.

Three routes: this tracker for the documented cases by class, the Bluetooth SIG's own venue and location pages for the official roster, and the venue itself — accessibility pages and on-site QR codes are where deployments announce themselves. Deployments change often enough that a venue check is worth the minute.

No — and no tracker is. It indexes deployments that are documented with dated, checkable sources, which means entries trail reality by however long reporting takes. The Bluetooth SIG's venue pages are the official roster; this page is the annotated map of the cases worth knowing by name.

A deployment appears here only with a named source and an access date — the Bluetooth SIG's venue write-ups and blog posts, the manufacturers' announcements, or trade press. Venue self-claims without documentation, and undocumented word of mouth, stay off the list.

The documented map

Auracast receivers

Which phones, hearing aids and earbuds can join an Auracast broadcast today — the receiving side of every deployment on this list.

View at blafili.com
Sources & verification
  • Bluetooth SIG blog, "15 venues around the world that are already supporting Auracast™ broadcasts" (Jason Marcel, November 26, 2025) — the 15-case pool this tracker indexes (Sydney Opera House, Stadium Taranaki, CCI at UAL, Grace Lutheran, Christ Presbyterian, Everyman, Blackfriars, Marriott Theatre, Regent Theatre, EUHA 2025, Daemyung Hearing Center, Akustik Schweiz and others). bluetooth.com/blog/15-venues-around-the-world-that-are-already-supporting-auracast-broadcasts/, accessed 2026-09-23
  • Bluetooth SIG blog, "Auracast™ broadcast audio takes off at Frankfurt Airport" (February 13, 2026) — first airport worldwide, gates A16/A17 Terminal 1. bluetooth.com/blog/auracast-broadcast-audio-takes-off-at-frankfurt-airport/, accessed 2026-09-23
  • Bluetooth SIG blog, "How Auracast™ broadcast audio is expanding" (December 10, 2025) — expansion outlook including public transportation systems, tourist attractions, visitor centers. bluetooth.com/blog/how-auracast-broadcast-audio-is-expanding/, accessed 2026-09-23
  • Hearing Review, "Auri Assistive Listening System Installed at Brighton Train Station in UK" (July 23, 2026); Ampetronic, Bristol Temple Meads and Vue Cinemas announcements. hearingreview.com + ampetronic.com, accessed 2026-09-23
Verified 2026-09-25 by blafili lab · report a correction