BIZTRAC BETA
Uoppgitt

HAMNAFOLKET HOLDING AS

Org. no. 933203417 Limited company (AS) Kinn Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −44,000
Equity NOK 1.7m
Incorporated 2023
Share capital NOK 51,000

Signals

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

HAMNAFOLKET HOLDING AS is registered as a limited company in Kinn, Vestland with organisation number 933203417. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 51,000, divided into 64 shares. The company's stated purpose is: “Investeringsvirksomhet og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også drive med kjøp/drift av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −44,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −44,000
Equity
NOK 1.7m
Est. value
NOK 1.5m

Financial health · 2025

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

Who owns HAMNAFOLKET HOLDING AS?

BRIGT OLAV SAMDAL
HAMNAFOLKET HOLDING AS
NOK 0 rev. · NOK −44,000 profit

HAMNAFOLKET HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HAMNAFOLKET HOLDING AS

Who owns HAMNAFOLKET HOLDING AS?

BRIGT OLAV SAMDAL is the largest registered owner, with 100.0%.

What is the revenue of HAMNAFOLKET HOLDING AS?

HAMNAFOLKET HOLDING AS had revenue of NOK 0 in 2024.

Where is HAMNAFOLKET HOLDING AS based?

HAMNAFOLKET HOLDING AS has its business address in Eikefjord.

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.