BIZTRAC BETA
Development of building projects

LIER BOLIGUTVIKLING AS

Org. no. 915508960 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 36.0m
Operating profit NOK −89,000
Equity NOK 953,000
Incorporated 2015
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−89k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LIER BOLIGUTVIKLING AS is registered as a limited company in Oslo, Oslo with organisation number 915508960. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2015. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 36.0m in revenue and NOK −89,000 in operating profit.

Key figures · 2024

Revenue
NOK 36.0m
Operating profit
NOK −89,000
Equity
NOK 953,000
Est. value
NOK 54.7m

Financial health · 2024

Liquidity
1.00
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.4%
Not satisfactory
Equity as a share of total capital

Who owns LIER BOLIGUTVIKLING AS?

SOLON BOLIG AS
LIER BOLIGUTVIKLING AS
NOK 36.0m rev. · NOK −89,000 profit

LIER BOLIGUTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LIER BOLIGUTVIKLING AS

Who owns LIER BOLIGUTVIKLING AS?

SOLON BOLIG AS is the largest registered owner, with 100.0%.

What is the revenue of LIER BOLIGUTVIKLING AS?

LIER BOLIGUTVIKLING AS had revenue of NOK 36.0m in 2024.

Where is LIER BOLIGUTVIKLING AS based?

LIER BOLIGUTVIKLING AS has its business address in Oslo.

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.