BIZTRAC BETA
Other passenger transport in coastal waters

ENGENBREEN SKYSS AS

Org. no. 915288820 Limited company (AS) Meløy Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 391,000
Operating profit NOK −40,000
Equity NOK −71,000
Incorporated 2015
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−71k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−40k kr).

ENGENBREEN SKYSS AS is registered as a limited company in Meløy, Nordland with organisation number 915288820. The business is classified under other passenger transport in coastal waters (NACE 50.109). The company was incorporated in 2015. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Persontransport, utvikle og investere i forretningsideer innenfor turisme og andre nærliggende næringer.”. The most recent filed accounts, for the 2024 financial year, show NOK 391,000 in revenue and NOK −40,000 in operating profit.

Key figures · 2024

Revenue
NOK 391,000
Operating profit
NOK −40,000
Equity
NOK −71,000

Financial health · 2024

Liquidity
2.55
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-12.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ENGENBREEN SKYSS AS?

EBS MELØY HOLDING AS
ENGENBREEN SKYSS AS
NOK 391,000 rev. · NOK −40,000 profit

ENGENBREEN SKYSS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ENGENBREEN SKYSS AS

Who owns ENGENBREEN SKYSS AS?

EBS MELØY HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ENGENBREEN SKYSS AS?

ENGENBREEN SKYSS AS had revenue of NOK 391,000 in 2024.

Where is ENGENBREEN SKYSS AS based?

ENGENBREEN SKYSS AS has its business address in Neverdal.

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.