BIZTRAC BETA
Rental and operating of own or leased real estate

UTLEIEBOLIG LILLEHAMMER AS

Org. no. 927150581 Limited company (AS) Ringsaker Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −36,000
Equity NOK −845,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−845k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−36k kr).

UTLEIEBOLIG LILLEHAMMER AS is registered as a limited company in Ringsaker, Innlandet with organisation number 927150581. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Eie, forvalte og leie ut boliger, og alt som dermed står i forbindelse.”.

Key figures · 2024

Operating profit
NOK −36,000
Equity
NOK −845,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns UTLEIEBOLIG LILLEHAMMER AS?

PPA EIENDOM AS
UTLEIEBOLIG LILLEHAMMER AS
· NOK −36,000 profit

UTLEIEBOLIG LILLEHAMMER AS has 1 registered shareholder:

All shareholders and roles →

Which companies does UTLEIEBOLIG LILLEHAMMER AS own?

UTLEIEBOLIG LILLEHAMMER AS holds a stake in 1 company:

See the full ownership structure →

Group structure

UTLEIEBOLIG LILLEHAMMER AS er morselskap for 7 datterselskaper:

Frequently asked questions about UTLEIEBOLIG LILLEHAMMER AS

Who owns UTLEIEBOLIG LILLEHAMMER AS?

PPA EIENDOM AS is the largest registered owner, with 100.0%.

Where is UTLEIEBOLIG LILLEHAMMER AS based?

UTLEIEBOLIG LILLEHAMMER AS has its business address in Brumunddal.

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.