biztrac. BETA
COMPANY REGISTER PROFILE
988420530 ORG. NO. 2025 ACCOUNTS 11 SECTIONS
Active UPDATED 03.10.2026
Beverage serving activities

PARKTEATRET BAR AS

Org. no. 988420530 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 33.8m
Operating profit NOK 2.5m
Equity NOK 2.7m
Incorporated 2005
Employees 70
Share capital NOK 100,000

PARKTEATRET BAR AS is registered as a limited company in Oslo, Oslo with organisation number 988420530. The business is classified under beverage serving activities (NACE 56.300). The company was incorporated in 2005 and has 70 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Drift av bar, kafe og restaurant samt alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 33.8m in revenue and NOK 2.5m in operating profit.

Former names: NYE PARKTEATRET BAR AS

Key figures · 2025

Revenue
NOK 33.8m
▲ +5 %
Operating profit
NOK 2.5m
▲ +22 %
Equity
NOK 2.7m
▲ +240 %
Est. value
NOK 10.0m

Financial health · 2025

Liquidity
1.67
Good
Current assets ÷ current liabilities
Profitability
25.5%
Very good
Return on total assets
Solidity
25.3%
Good
Equity as a share of total capital

Who owns PARKTEATRET BAR AS?

PARKTEATRET BAR AS
NOK 33.8m rev. · NOK 2.5m profit

PARKTEATRET BAR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PARKTEATRET BAR AS

Who owns PARKTEATRET BAR AS?

GRÜNERLØKKA KULTURHUS AS is the largest registered owner, with 100.0%.

What is the revenue of PARKTEATRET BAR AS?

PARKTEATRET BAR AS had revenue of NOK 33.8m in 2025.

Who is the general manager of PARKTEATRET BAR AS?

Ruben Normann Karlsen is registered as general manager of PARKTEATRET BAR AS.

Where is PARKTEATRET BAR AS based?

PARKTEATRET BAR 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.