BIZTRAC BETA
Rental and operating of own or leased real estate

NORTHSEA ADVENTURE AS

Org. no. 999659608 Limited company (AS) Holmestrand Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 320,000
Operating profit NOK 230,000
Equity NOK −974,000
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−974k kr).

NORTHSEA ADVENTURE AS is registered as a limited company in Holmestrand, Vestfold with organisation number 999659608. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Eiendomsinvesteringer, eiendomsutvikling, utleievirksomhet av eiendom, samt annet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 320,000 in revenue and NOK 230,000 in operating profit.

Key figures · 2025

Revenue
NOK 320,000
Operating profit
NOK 230,000
Equity
NOK −974,000
Est. value
NOK 1.8m

Financial health · 2025

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

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

Who owns NORTHSEA ADVENTURE AS?

M.ALGRØY AS
NORTHSEA ADVENTURE AS
NOK 320,000 rev. · NOK 230,000 profit

NORTHSEA ADVENTURE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORTHSEA ADVENTURE AS

Who owns NORTHSEA ADVENTURE AS?

M.ALGRØY AS is the largest registered owner, with 100.0%.

What is the revenue of NORTHSEA ADVENTURE AS?

NORTHSEA ADVENTURE AS had revenue of NOK 320,000 in 2025.

Where is NORTHSEA ADVENTURE AS based?

NORTHSEA ADVENTURE AS has its business address in Hof.

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.