BIZTRAC BETA
Development of building projects

FINNKROKEN EIENDOM AS

Org. no. 933111997 Limited company (AS) Karlsøy Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 24,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5k kr).

FINNKROKEN EIENDOM AS is registered as a limited company in Karlsøy, Troms with organisation number 933111997. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utvikling og salg av hyttetomter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 24,000
Est. value
NOK 22,000

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

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

Who owns FINNKROKEN EIENDOM AS?

FINNKROKEN FERIEHYTTER AS
FINNKROKEN EIENDOM AS
NOK 0 rev. · NOK −5,000 profit

FINNKROKEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FINNKROKEN EIENDOM AS

Who owns FINNKROKEN EIENDOM AS?

FINNKROKEN FERIEHYTTER AS is the largest registered owner, with 100.0%.

What is the revenue of FINNKROKEN EIENDOM AS?

FINNKROKEN EIENDOM AS had revenue of NOK 0 in 2025.

Who is the general manager of FINNKROKEN EIENDOM AS?

Geir Pettersen is registered as general manager of FINNKROKEN EIENDOM AS.

Where is FINNKROKEN EIENDOM AS based?

FINNKROKEN EIENDOM AS has its business address in Stakkvik.

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.