BIZTRAC BETA
Construction of residential and non-residential buildings

LIABYGG AS

Org. no. 922710406 Limited company (AS) Skien Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 19.2m
Operating profit NOK 2.7m
Equity NOK 10.0m
Incorporated 2019
Employees 8
Share capital NOK 500,000

LIABYGG AS is registered as a limited company in Skien, Telemark with organisation number 922710406. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2019 and has 8 registered employees. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Nybygg og rehabilitering av bygg, samt kjøp, salg og utvikling av fast eiendom og det som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 19.2m in revenue and NOK 2.7m in operating profit.

Key figures · 2025

Revenue
NOK 19.2m
Operating profit
NOK 2.7m
Equity
NOK 10.0m
Est. value
NOK 13.1m

Financial health · 2025

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

Who owns LIABYGG AS?

JOHANSSON HOLDING AS
LIABYGG AS
NOK 19.2m rev. · NOK 2.7m profit

LIABYGG AS has 2 registered shareholders:

All shareholders and roles →

Which companies does LIABYGG AS own?

LIABYGG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LIABYGG AS

Who owns LIABYGG AS?

JOHANSSON HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of LIABYGG AS?

LIABYGG AS had revenue of NOK 19.2m in 2025.

Who is the general manager of LIABYGG AS?

Eric Johansson is registered as general manager of LIABYGG AS.

Where is LIABYGG AS based?

LIABYGG AS has its business address in Skien.

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.