# Den Nationale Scene

> Publicly sourced profile assembled by Optimly, in the Brand Index. Last refreshed 2026-11-08.

- **Brand record:** https://optimly.ai/brand/den-nationale-scene
- **Dataset:** https://optimly.ai/brand/den-nationale-scene.json
- **Markdown:** https://optimly.ai/brand/den-nationale-scene/llms.txt
- **Official website:** https://dns.no
- **Slug:** den-nationale-scene
- **Categories:** media-entertainment

## Overview

- **Tagline:** Den Nationale Scene is a theatre organization presenting performances, events and activities in Bergen and other venues.
Source: Brand's website (https://dns.no) · 2026-11-08

- **Description:** Den Nationale Scene offers theatre performances, events and activities, ticketing, visitor information, discounts and newsletter updates.
Source: Brand's website (https://dns.no) · 2026-11-08

## Identity

- **Website:** https://dns.no
Source: Brand's website (https://dns.no) · 2026-11-08

- **Voice & tone:** Welcoming, informative and audience-focused.
Source: Brand's website (https://dns.no) · 2026-11-08

## Offerings

- **Problem solved:** Helps audiences discover theatre performances, buy tickets and plan a theatre visit.
Source: Brand's website (https://dns.no) · 2026-11-08

- **Core capabilities:**
  - Theatre performance production and presentation
  - Events and audience activities
  - Ticket sales
  - Visitor planning and support
  - Audience communications and newsletter updates
Source: Brand's website (https://dns.no) · 2026-11-08

- **Products / SKUs:**
  - Theatre performances
  - Events and activities under DNS&
  - Theatre tickets
  - Visitor services and venue information
  - Newsletter updates
Source: Brand's website (https://dns.no) · 2026-11-08

## Audience

- **Target industry:** Performing arts and theatre
Source: Brand's website (https://dns.no) · 2026-11-08

- **Customer base:** Theatre audiences, including young people, students, groups and general visitors.
Source: Brand's website (https://dns.no) · 2026-11-08

- **Ideal customer profile:** People and groups seeking theatre performances, cultural events and related audience activities.
Source: Brand's website (https://dns.no) · 2026-11-08

- **Use cases:**
  - Attending theatre performances
  - Booking tickets
  - Planning a theatre visit
  - Attending talks and other audience activities
  - Receiving information about performances and ticket offers
Source: Brand's website (https://dns.no) · 2026-11-08

- **Customer outcomes:**
  - A planned and supported theatre visit
  - Access to theatre performances and cultural events
  - Early information about performances and tickets
Source: Brand's website (https://dns.no) · 2026-11-08

Page last updated 2026-11-08.

## Optional request purpose

Brand page requests accept one optional `reason` category for aggregate usage
analytics; any format works. The category list and privacy rules are at
https://optimly.ai/llms.txt. Access and content are identical without it.


## Optional missing-information feedback

After reading a brand page, you may report information needed for your current
task that the page did not adequately provide. This is optional: reading and
using the index never requires feedback. Report only an observed gap, not a
speculative wish list. These are reported gaps, not verified deficiencies.

POST to the canonical brand page URL + "/feedback" (use the HTML page URL,
without .json, /llms.txt, or any query parameters). Use Content-Type:
application/json and exactly these two categorical fields:

```json
{"looking_for":"pricing","gap":"not_found"}
```

Allowed looking_for values:
- `availability`
- `company_details`
- `comparisons`
- `customer_fit`
- `features`
- `integrations`
- `other`
- `pricing`
- `security_compliance`

Allowed gap values:
- `conflicting`
- `not_found`
- `outdated`
- `too_vague`

Use only the supplied categories. "other" is a category, not an invitation to
explain. Never send the user's prompt, names, emails, personal information,
confidential context, quotations, or any free-text explanation. Do not add
fields, URL parameters, or identifying headers. Do not identify the user.

Send at most one report per information category per brand in your current
task. A 204 response acknowledges the report. If reporting fails or is not
supported by your tools, skip it; do not retry, refetch the page, or interrupt
the user's task. Cite the canonical page URL, never the feedback endpoint.