BIZTRAC BETA
Restaurant activities

BURGERHEIM BERGEN AS

Org. no. 933219658 Limited company (AS) Bergen Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 2.0m
Operating profit NOK −354,000
Equity NOK 1.8m
Incorporated 2024
Employees 17
Share capital NOK 230,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−354k kr).

BURGERHEIM BERGEN AS is registered as a limited company in Bergen, Vestland with organisation number 933219658. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2024 and has 17 registered employees. Registered share capital is NOK 230,000, divided into 23000 shares. The company's stated purpose is: “Produksjon og salg av burger, og det som faller inn under denne typen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.0m in revenue and NOK −354,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.0m
Operating profit
NOK −354,000
Equity
NOK 1.8m
Est. value
NOK 2.3m

Financial health · 2024

Liquidity
1.59
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
68.2%
Very good
Equity as a share of total capital

Who owns BURGERHEIM BERGEN AS?

FLAMME BURGER HOLDING AS
BURGERHEIM BERGEN AS
NOK 2.0m rev. · NOK −354,000 profit

BURGERHEIM BERGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BURGERHEIM BERGEN AS

Who owns BURGERHEIM BERGEN AS?

FLAMME BURGER HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BURGERHEIM BERGEN AS?

BURGERHEIM BERGEN AS had revenue of NOK 2.0m in 2024.

Who is the general manager of BURGERHEIM BERGEN AS?

Hans Rabben Ruud is registered as general manager of BURGERHEIM BERGEN AS.

Where is BURGERHEIM BERGEN AS based?

BURGERHEIM BERGEN AS has its business address in Bergen.

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.