biztrac. BETA
COMPANY REGISTER PROFILE
987903937 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

THEATERCAFEEN AS

Org. no. 987903937 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 106.1m
Operating profit NOK 2.1m
Equity NOK 5.4m
Incorporated 2005
Employees 136
Share capital NOK 1.1m

THEATERCAFEEN AS is registered as a limited company in Oslo, Oslo with organisation number 987903937. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2005 and has 136 registered employees. Registered share capital is NOK 1.1m, divided into 11400 shares. The company's stated purpose is: “Cafe- og restaurantdrift og hva som dermed står i naturlig forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 106.1m in revenue and NOK 2.1m in operating profit.

Former names: STARTUP 12 AS

Key figures · 2025

Revenue
NOK 106.1m
▲ +4 %
Operating profit
NOK 2.1m
▼ −23 %
Equity
NOK 5.4m
▲ +5 %
Est. value
NOK 9.8m

Financial health · 2025

Liquidity
1.01
Satisfactory
Current assets ÷ current liabilities
Profitability
4.7%
Weak
Return on total assets
Solidity
11.2%
Satisfactory
Equity as a share of total capital

Who owns THEATERCAFEEN AS?

THEATERCAFEEN AS
NOK 106.1m rev. · NOK 2.1m profit

THEATERCAFEEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about THEATERCAFEEN AS

Who owns THEATERCAFEEN AS?

HOTELL- OG RESTAURANTHUSET CONTINENTAL AS is the largest registered owner, with 100.0%.

What is the revenue of THEATERCAFEEN AS?

THEATERCAFEEN AS had revenue of NOK 106.1m in 2025.

Who is the general manager of THEATERCAFEEN AS?

Elisabeth Caroline Brochmann is registered as general manager of THEATERCAFEEN AS.

Where is THEATERCAFEEN AS based?

THEATERCAFEEN AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.