BIZTRAC BETA
Uoppgitt

LIRE HOLDING AS

Org. no. 932950561 Limited company (AS) Øvre Eiker Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −13,000
Equity NOK 44,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−13k kr).

LIRE HOLDING AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 932950561. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering i aksjer og andeler i andre selskaper, investering i fast eiendom og annen næringsvirksomhet og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −13,000
Equity
NOK 44,000
Est. value
NOK 113,000

Financial health · 2024

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

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

Who owns LIRE HOLDING AS?

LINDA BORGERSEN SKJERSÅKER
LIRE HOLDING AS
NOK 0 rev. · NOK −13,000 profit

LIRE HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does LIRE HOLDING AS own?

LIRE HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LIRE HOLDING AS

Who owns LIRE HOLDING AS?

LINDA BORGERSEN SKJERSÅKER is the largest registered owner, with 50.0%.

What is the revenue of LIRE HOLDING AS?

LIRE HOLDING AS had revenue of NOK 0 in 2024.

Where is LIRE HOLDING AS based?

LIRE HOLDING AS has its business address in Hokksund.

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.