BIZTRAC BETA
COMPANY REGISTER PROFILE
916551797 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Other captive investment companies

LEIRIN HOLDING AS

Org. no. 916551797 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −114,000
Equity NOK 1.8m
Incorporated 2016
Share capital NOK 2.2m

Signals

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

LEIRIN HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 916551797. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2016. Registered share capital is NOK 2.2m, divided into 20000 shares. The company's stated purpose is: “Investeringer i aksjer, virksomheter, finansielle instrumenter og eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −114,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −114,000
Equity
NOK 1.8m
Est. value
NOK 1.6m

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.2%
Good
Equity as a share of total capital

Who owns LEIRIN HOLDING AS?

EIVIND SVERDRUP
LEIRIN HOLDING AS
NOK 0 rev. · NOK −114,000 profit

LEIRIN HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does LEIRIN HOLDING AS own?

LEIRIN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LEIRIN HOLDING AS

Who owns LEIRIN HOLDING AS?

EIVIND SVERDRUP is the largest registered owner, with 51.0%.

What is the revenue of LEIRIN HOLDING AS?

LEIRIN HOLDING AS had revenue of NOK 0 in 2024.

Where is LEIRIN HOLDING AS based?

LEIRIN HOLDING 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.