BIZTRAC BETA
Uoppgitt

EIRINS HOLDING AS

Org. no. 926311360 Limited company (AS) Trondheim Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −40,000
Equity NOK 49.5m
Incorporated 2020
Share capital NOK 30,000

Signals

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

EIRINS HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 926311360. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investering i aksjer, obligasjoner og andre verdipapirer samt å erverve, forvalte og utvikle fast eiendom og det som dermed er forbundet, herunder deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −40,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −40,000
Equity
NOK 49.5m
Est. value
NOK 58.2m

Financial health · 2024

Liquidity
4.87
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
99.7%
Very good
Equity as a share of total capital

Who owns EIRINS HOLDING AS?

EIRIN BAKKEN SOLBERG
EIRINS HOLDING AS
NOK 0 rev. · NOK −40,000 profit

EIRINS HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EIRINS HOLDING AS own?

EIRINS HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EIRINS HOLDING AS

Who owns EIRINS HOLDING AS?

EIRIN BAKKEN SOLBERG is the largest registered owner, with 100.0%.

What is the revenue of EIRINS HOLDING AS?

EIRINS HOLDING AS had revenue of NOK 0 in 2024.

Where is EIRINS HOLDING AS based?

EIRINS HOLDING AS has its business address in Charlottenlund.

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.