BIZTRAC BETA
Marine fishing

KALVENAKKEN AS

Org. no. 926186809 Limited company (AS) Tromsø Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −23,000
Equity NOK 26.3m
Incorporated 2020
Share capital NOK 43,000

Signals

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

KALVENAKKEN AS is registered as a limited company in Tromsø, Troms with organisation number 926186809. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2020. Registered share capital is NOK 43,000, divided into 9900 shares. The company's stated purpose is: “Å eie aksjer, investere i og utvikle fast eiendom samt annen virksomhet som naturlig faller inn under dette, herunder delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −23,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −23,000
Equity
NOK 26.3m
Est. value
NOK 60.5m

Financial health · 2024

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

Who owns KALVENAKKEN AS?

TOMMY HANSEN
KALVENAKKEN AS
NOK 0 rev. · NOK −23,000 profit

KALVENAKKEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KALVENAKKEN AS own?

KALVENAKKEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KALVENAKKEN AS

Who owns KALVENAKKEN AS?

TOMMY HANSEN is the largest registered owner, with 100.0%.

What is the revenue of KALVENAKKEN AS?

KALVENAKKEN AS had revenue of NOK 0 in 2024.

Who is the general manager of KALVENAKKEN AS?

Tommy Hansen is registered as general manager of KALVENAKKEN AS.

Where is KALVENAKKEN AS based?

KALVENAKKEN AS has its business address in Sommarøya.

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.