BIZTRAC BETA
Uoppgitt

HOLMSUNDET HOLDING AS

Org. no. 933967050 Limited company (AS) Flatanger Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 173,000
Operating profit NOK 100,000
Equity NOK 223,000
Incorporated 2024
Share capital NOK 150,000

HOLMSUNDET HOLDING AS is registered as a limited company in Flatanger, Trøndelag with organisation number 933967050. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Investering i eiendom og aksjer, samt rådgivningsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 173,000 in revenue and NOK 100,000 in operating profit.

Key figures · 2024

Revenue
NOK 173,000
Operating profit
NOK 100,000
Equity
NOK 223,000
Est. value
NOK 433,000

Financial health · 2024

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

Who owns HOLMSUNDET HOLDING AS?

KAI ERLING STAVEN
HOLMSUNDET HOLDING AS
NOK 173,000 rev. · NOK 100,000 profit

HOLMSUNDET HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HOLMSUNDET HOLDING AS own?

HOLMSUNDET HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HOLMSUNDET HOLDING AS

Who owns HOLMSUNDET HOLDING AS?

KAI ERLING STAVEN is the largest registered owner, with 100.0%.

What is the revenue of HOLMSUNDET HOLDING AS?

HOLMSUNDET HOLDING AS had revenue of NOK 173,000 in 2024.

Who is the general manager of HOLMSUNDET HOLDING AS?

Kai Erling Staven is registered as general manager of HOLMSUNDET HOLDING AS.

Where is HOLMSUNDET HOLDING AS based?

HOLMSUNDET HOLDING AS has its business address in Flatanger.

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.