BIZTRAC BETA
Beverage serving activities

HEIDI'S BIER BAR OSLO AS

Org. no. 915807208 Limited company (AS) Kristiansand Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 31.5m
Operating profit NOK 3.5m
Equity NOK 2.5m
Incorporated 2015
Employees 33
Share capital NOK 500,000

HEIDI'S BIER BAR OSLO AS is registered as a limited company in Kristiansand, Agder with organisation number 915807208. The business is classified under beverage serving activities (NACE 56.300). The company was incorporated in 2015 and has 33 registered employees. Registered share capital is NOK 500,000, divided into 100 shares. The company's stated purpose is: “Bar- og restaurantdrift.”. The most recent filed accounts, for the 2024 financial year, show NOK 31.5m in revenue and NOK 3.5m in operating profit.

Key figures · 2024

Revenue
NOK 31.5m
Operating profit
NOK 3.5m
Equity
NOK 2.5m
Est. value
NOK 13.2m

Financial health · 2024

Liquidity
0.19
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
14.5%
Satisfactory
Equity as a share of total capital

Who owns HEIDI'S BIER BAR OSLO AS?

REKOM NORGE AS
HEIDI'S BIER BAR OSLO AS
NOK 31.5m rev. · NOK 3.5m profit

HEIDI'S BIER BAR OSLO AS has 1 registered shareholder:

All shareholders and roles →

Group structure

HEIDI'S BIER BAR OSLO AS er morselskap for 33 datterselskaper:

Frequently asked questions about HEIDI'S BIER BAR OSLO AS

Who owns HEIDI'S BIER BAR OSLO AS?

REKOM NORGE AS is the largest registered owner, with 100.0%.

What is the revenue of HEIDI'S BIER BAR OSLO AS?

HEIDI'S BIER BAR OSLO AS had revenue of NOK 31.5m in 2024.

Who is the general manager of HEIDI'S BIER BAR OSLO AS?

Jonathan Andreas Grumme is registered as general manager of HEIDI'S BIER BAR OSLO AS.

Where is HEIDI'S BIER BAR OSLO AS based?

HEIDI'S BIER BAR OSLO AS has its business address in Kristiansand S.

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

Report a problem

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