BIZTRAC BETA
COMPANY REGISTER PROFILE
932359790 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 02.09.2026
Construction of residential and non-residential buildings

KROGSET BYGG AS

Org. no. 932359790 Limited company (AS) Vestnes Incorporated 1982 Active
Ownership graph ↗
Revenue 2025 NOK 3.5m
Operating profit NOK 662,000
Equity NOK 699,000
Incorporated 1982
Share capital NOK 100,000

KROGSET BYGG AS is registered as a limited company in Vestnes, Møre og Romsdal with organisation number 932359790. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1982. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Bygningsarbeid med nybygg og rehabilitering og alt hva dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.5m in revenue and NOK 662,000 in operating profit.

Former names: KROGSET SAGBRUK AS

Key figures · 2025

Revenue
NOK 3.5m
▼ −23 %
Operating profit
NOK 662,000
▲ +396 %
Equity
NOK 699,000
▲ +183 %
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
0.58
Weak
Current assets ÷ current liabilities
Profitability
33.0%
Very good
Return on total assets
Solidity
37.8%
Good
Equity as a share of total capital

Who owns KROGSET BYGG AS?

KROGSET BYGG AS
NOK 3.5m rev. · NOK 662,000 profit

KROGSET BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KROGSET BYGG AS

Who owns KROGSET BYGG AS?

KROGSET AS is the largest registered owner, with 77.5%.

What is the revenue of KROGSET BYGG AS?

KROGSET BYGG AS had revenue of NOK 3.5m in 2025.

Who is the general manager of KROGSET BYGG AS?

Bernt Kristian Aas is registered as general manager of KROGSET BYGG AS.

Where is KROGSET BYGG AS based?

KROGSET BYGG AS has its business address in Vikebukt.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.