BIZTRAC BETA
Restaurant activities

SJØFLYHAVNA KRO AS

Org. no. 993173541 Limited company (AS) Bærum Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 21.2m
Operating profit NOK −226,000
Equity NOK 216,000
Incorporated 2008
Employees 19
Share capital NOK 600,000

Signals

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

SJØFLYHAVNA KRO AS is registered as a limited company in Bærum, Akershus with organisation number 993173541. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2008 and has 19 registered employees. Registered share capital is NOK 600,000, divided into 2000 shares. The company's stated purpose is: “Bar- og restaurantdrift på Sjøflyhavna Kro. Import og eksport av mat og drikkevarer. Cateringvirksomhet og bevertning ved kulturarrangementer. Samt handel og deltakelse i andre selskaper med lignende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 21.2m in revenue and NOK −226,000 in operating profit.

Key figures · 2024

Revenue
NOK 21.2m
Operating profit
NOK −226,000
Equity
NOK 216,000
Est. value
NOK 14.5m

Financial health · 2024

Liquidity
0.74
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
5.0%
Weak
Equity as a share of total capital

Who owns SJØFLYHAVNA KRO AS?

OSLO MEKANISKE VERKSTED AS
SJØFLYHAVNA KRO AS
NOK 21.2m rev. · NOK −226,000 profit

SJØFLYHAVNA KRO AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about SJØFLYHAVNA KRO AS

Who owns SJØFLYHAVNA KRO AS?

OSLO MEKANISKE VERKSTED AS is the largest registered owner, with 33.3%.

What is the revenue of SJØFLYHAVNA KRO AS?

SJØFLYHAVNA KRO AS had revenue of NOK 21.2m in 2024.

Where is SJØFLYHAVNA KRO AS based?

SJØFLYHAVNA KRO AS has its business address in Fornebu.

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.