BIZTRAC BETA
Rental and operating of own or leased real estate

AWO CONSULTING AS

Org. no. 912747131 Limited company (AS) Kristiansund Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 129,000
Operating profit NOK 50,000
Equity NOK 11.5m
Incorporated 2013
Share capital NOK 862,000

AWO CONSULTING AS is registered as a limited company in Kristiansund, Møre og Romsdal with organisation number 912747131. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 862,000, divided into 862 shares. The company's stated purpose is: “Investering i aksjer og eiendommer, investering i andre selskap i tilknytning til slik virksomhet, samt salg av tjenester på områder hvor selskapet har kompetanse.”. The most recent filed accounts, for the 2025 financial year, show NOK 129,000 in revenue and NOK 50,000 in operating profit.

Key figures · 2025

Revenue
NOK 129,000
Operating profit
NOK 50,000
Equity
NOK 11.5m
Est. value
NOK 8.1m

Financial health · 2025

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

Who owns AWO CONSULTING AS?

LIV HALFRID LUND OLSEN
AWO CONSULTING AS
NOK 129,000 rev. · NOK 50,000 profit

AWO CONSULTING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does AWO CONSULTING AS own?

AWO CONSULTING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AWO CONSULTING AS

Who owns AWO CONSULTING AS?

LIV HALFRID LUND OLSEN is the largest registered owner, with 52.2%.

What is the revenue of AWO CONSULTING AS?

AWO CONSULTING AS had revenue of NOK 129,000 in 2025.

Where is AWO CONSULTING AS based?

AWO CONSULTING AS has its business address in Kristiansund N.

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.