BIZTRAC BETA
Construction of residential and non-residential buildings

KRONBYGG AS

Org. no. 911918242 Limited company (AS) Øygarden Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 5.9m
Operating profit NOK 201,000
Equity NOK 1.0m
Incorporated 2013
Share capital NOK 30,000

KRONBYGG AS is registered as a limited company in Øygarden, Vestland with organisation number 911918242. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Fremstilling/salg av nybygg, påbygg, vedlikehold, rehabilitering av bygg og andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.9m in revenue and NOK 201,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.9m
Operating profit
NOK 201,000
Equity
NOK 1.0m
Est. value
NOK 1.2m

Financial health · 2024

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

Who owns KRONBYGG AS?

ARVID VIK
KRONBYGG AS
NOK 5.9m rev. · NOK 201,000 profit

KRONBYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KRONBYGG AS

Who owns KRONBYGG AS?

ARVID VIK is the largest registered owner, with 50.0%.

What is the revenue of KRONBYGG AS?

KRONBYGG AS had revenue of NOK 5.9m in 2024.

Who is the general manager of KRONBYGG AS?

Arvid Vik is registered as general manager of KRONBYGG AS.

Where is KRONBYGG AS based?

KRONBYGG AS has its business address in Rong.

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.