BIZTRAC BETA
Rental and operating of own or leased real estate

LENUM BOLIG AS

Org. no. 981170342 Limited company (AS) Skien Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 5.8m
Operating profit NOK 3.6m
Equity NOK 15.1m
Incorporated 1999
Share capital NOK 17.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LENUM BOLIG AS is registered as a limited company in Skien, Telemark with organisation number 981170342. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1999. Registered share capital is NOK 17.0m, divided into 200 shares. The company's stated purpose is: “Kjøp og salg av aksjer og fast eiendom, utleie av fast eiendom samt konsultativ bistand innenfor disse områder.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.8m in revenue and NOK 3.6m in operating profit.

Key figures · 2024

Revenue
NOK 5.8m
Operating profit
NOK 3.6m
Equity
NOK 15.1m
Est. value
NOK 16.4m

Financial health · 2024

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

Who owns LENUM BOLIG AS?

HIBERNIAN HOLDING AS
LENUM BOLIG AS
NOK 5.8m rev. · NOK 3.6m profit

LENUM BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LENUM BOLIG AS own?

LENUM BOLIG AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LENUM BOLIG AS

Who owns LENUM BOLIG AS?

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

What is the revenue of LENUM BOLIG AS?

LENUM BOLIG AS had revenue of NOK 5.8m in 2024.

Where is LENUM BOLIG AS based?

LENUM BOLIG 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.