BIZTRAC BETA
Construction of residential and non-residential buildings

A.O.KLEIVE BYGG AS

Org. no. 930605972 Limited company (AS) Molde Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 5.7m
Operating profit NOK 83,000
Equity NOK 564,000
Incorporated 2022
Employees 9
Share capital NOK 30,000

A.O.KLEIVE BYGG AS is registered as a limited company in Molde, Møre og Romsdal with organisation number 930605972. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2022 and has 9 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Snekker, påbygg, restaurering, nybygg og ferdighus, og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.7m in revenue and NOK 83,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.7m
Operating profit
NOK 83,000
Equity
NOK 564,000
Est. value
NOK 531,000

Financial health · 2025

Liquidity
1.50
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
36.0%
Good
Equity as a share of total capital

Who owns A.O.KLEIVE BYGG AS?

ARNT OVE KLEIVE
A.O.KLEIVE BYGG AS
NOK 5.7m rev. · NOK 83,000 profit

A.O.KLEIVE BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about A.O.KLEIVE BYGG AS

Who owns A.O.KLEIVE BYGG AS?

ARNT OVE KLEIVE is the largest registered owner, with 90.0%.

What is the revenue of A.O.KLEIVE BYGG AS?

A.O.KLEIVE BYGG AS had revenue of NOK 5.7m in 2025.

Who is the general manager of A.O.KLEIVE BYGG AS?

Arnt Ove Kleive is registered as general manager of A.O.KLEIVE BYGG AS.

Where is A.O.KLEIVE BYGG AS based?

A.O.KLEIVE BYGG AS has its business address in Eidsvåg I Romsdal.

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.