BIZTRAC BETA
Rental and operating of own or leased real estate

LIERBAKKENE AS

Org. no. 921828195 Limited company (AS) Lier Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 4.8m
Operating profit NOK 2.4m
Equity NOK 6.4m
Incorporated 2018
Share capital NOK 1.0m

LIERBAKKENE AS is registered as a limited company in Lier, Buskerud with organisation number 921828195. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 1.0m, divided into 100 shares. The company's stated purpose is: “Utøve næringsvirksomhet ved erverv og drift/salg av fast eiendom samt drive utleie av eiendom, deltagelse i andre foretak og det som naturlig står i forbindelse hermed. Samt investeringer og aksjer.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.8m in revenue and NOK 2.4m in operating profit.

Key figures · 2024

Revenue
NOK 4.8m
Operating profit
NOK 2.4m
Equity
NOK 6.4m
Est. value
NOK 6.8m

Financial health · 2024

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

Who owns LIERBAKKENE AS?

RUBA INVEST AS
LIERBAKKENE AS
NOK 4.8m rev. · NOK 2.4m profit

LIERBAKKENE AS has 1 registered shareholder:

All shareholders and roles →

Group structure

LIERBAKKENE AS er morselskap for 4 datterselskaper:

Frequently asked questions about LIERBAKKENE AS

Who owns LIERBAKKENE AS?

RUBA INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of LIERBAKKENE AS?

LIERBAKKENE AS had revenue of NOK 4.8m in 2024.

Who is the general manager of LIERBAKKENE AS?

Rune Halstensen is registered as general manager of LIERBAKKENE AS.

Where is LIERBAKKENE AS based?

LIERBAKKENE AS has its business address in Lier.

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.