BIZTRAC BETA
Rental and operating of own or leased real estate

LOGIN PARINVEST HOLDING AS

Org. no. 922704538 Limited company (AS) Trondheim Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −151,000
Equity NOK 2.4bn
Incorporated 2019
Share capital NOK 200,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−151k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LOGIN PARINVEST HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 922704538. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 200,000, divided into 200000 shares. The company's stated purpose is: “Selskapets virksomhet er å investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”.

Key figures · 2024

Operating profit
NOK −151,000
Equity
NOK 2.4bn
Est. value
NOK 1.8bn

Financial health · 2025

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

Who owns LOGIN PARINVEST HOLDING AS?

RELOG AS
LOGIN PARINVEST HOLDING AS
· NOK −151,000 profit

LOGIN PARINVEST HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does LOGIN PARINVEST HOLDING AS own?

LOGIN PARINVEST HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LOGIN PARINVEST HOLDING AS

Who owns LOGIN PARINVEST HOLDING AS?

RELOG AS is the largest registered owner, with 70.0%.

Where is LOGIN PARINVEST HOLDING AS based?

LOGIN PARINVEST HOLDING AS has its business address in Trondheim.

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.