BIZTRAC BETA
Construction of residential and non-residential buildings

LIABØ ENTREPRENØR AS

Org. no. 916036736 Limited company (AS) Kristiansund Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 41.2m
Operating profit NOK 3.7m
Equity NOK 8.8m
Incorporated 2015
Employees 19
Share capital NOK 1.0m

LIABØ ENTREPRENØR AS is registered as a limited company in Kristiansund, Møre og Romsdal with organisation number 916036736. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2015 and has 19 registered employees. Registered share capital is NOK 1.0m, divided into 10000 shares. The company's stated purpose is: “Entreprenørvirksomhet innen bygg og anlegg og hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 41.2m in revenue and NOK 3.7m in operating profit.

Key figures · 2025

Revenue
NOK 41.2m
Operating profit
NOK 3.7m
Equity
NOK 8.8m
Est. value
NOK 17.3m

Financial health · 2025

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

Who owns LIABØ ENTREPRENØR AS?

LIABØ HOLDING AS
LIABØ ENTREPRENØR AS
NOK 41.2m rev. · NOK 3.7m profit

LIABØ ENTREPRENØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LIABØ ENTREPRENØR AS

Who owns LIABØ ENTREPRENØR AS?

LIABØ HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LIABØ ENTREPRENØR AS?

LIABØ ENTREPRENØR AS had revenue of NOK 41.2m in 2025.

Who is the general manager of LIABØ ENTREPRENØR AS?

Øyvind Roger Liabø is registered as general manager of LIABØ ENTREPRENØR AS.

Where is LIABØ ENTREPRENØR AS based?

LIABØ ENTREPRENØR 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.