BIZTRAC BETA
Rental and operating of own or leased real estate

JAKOBSLIVEGEN 7 EIENDOM AS

Org. no. 820875842 Limited company (AS) Trondheim Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 393,000
Operating profit NOK −11,000
Equity NOK 7.7m
Incorporated 2018
Share capital NOK 100,000

Signals

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

JAKOBSLIVEGEN 7 EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 820875842. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 100,000, divided into 1 shares. The company's stated purpose is: “Utvikling, forvaltning og salg av fast eiendom og annen virksomhet som er beslektet med denne.”. The most recent filed accounts, for the 2024 financial year, show NOK 393,000 in revenue and NOK −11,000 in operating profit.

Key figures · 2024

Revenue
NOK 393,000
Operating profit
NOK −11,000
Equity
NOK 7.7m
Est. value
NOK 7.0m

Financial health · 2024

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

Who owns JAKOBSLIVEGEN 7 EIENDOM AS?

I K LYKKE EIENDOM HOLDING AS
JAKOBSLIVEGEN 7 EIENDOM AS
NOK 393,000 rev. · NOK −11,000 profit

JAKOBSLIVEGEN 7 EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JAKOBSLIVEGEN 7 EIENDOM AS

Who owns JAKOBSLIVEGEN 7 EIENDOM AS?

I K LYKKE EIENDOM HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of JAKOBSLIVEGEN 7 EIENDOM AS?

JAKOBSLIVEGEN 7 EIENDOM AS had revenue of NOK 393,000 in 2024.

Where is JAKOBSLIVEGEN 7 EIENDOM AS based?

JAKOBSLIVEGEN 7 EIENDOM 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.