BIZTRAC BETA
Development of building projects

KRÅKO UTVIKLING AS

Org. no. 988174254 Limited company (AS) Fitjar Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK 621,000
Equity NOK 1.1m
Incorporated 2005
Share capital NOK 105,000

KRÅKO UTVIKLING AS is registered as a limited company in Fitjar, Vestland with organisation number 988174254. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2005. Registered share capital is NOK 105,000, divided into 21000 shares. The company's stated purpose is: “Byggja ut og drifta fellesanlegg for Kråko-området og verksemd knytta til dette. Gjennomføra marknadsretta tiltak/aktivitetar som støttar opp om selskapet si verksemd. Selskapet kan eiga/ha eigarandel i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK 621,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.0m
Operating profit
NOK 621,000
Equity
NOK 1.1m
Est. value
NOK 2.4m

Financial health · 2025

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

Who owns KRÅKO UTVIKLING AS?

DALEN EIGEDOMSUTVIKLING AS
KRÅKO UTVIKLING AS
NOK 3.0m rev. · NOK 621,000 profit

KRÅKO UTVIKLING AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about KRÅKO UTVIKLING AS

Who owns KRÅKO UTVIKLING AS?

DALEN EIGEDOMSUTVIKLING AS is the largest registered owner, with 28.3%.

What is the revenue of KRÅKO UTVIKLING AS?

KRÅKO UTVIKLING AS had revenue of NOK 3.0m in 2025.

Who is the general manager of KRÅKO UTVIKLING AS?

Johannes Sandvik is registered as general manager of KRÅKO UTVIKLING AS.

Where is KRÅKO UTVIKLING AS based?

KRÅKO UTVIKLING AS has its business address in Fitjar.

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.