BIZTRAC BETA
Rental and operating of own or leased real estate

LYKKEBORGEN AS

Org. no. 988455857 Limited company (AS) Trondheim Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 971,000
Operating profit NOK −1.7m
Equity NOK 145.3m
Incorporated 2005
Share capital NOK 4.5m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,7 mill kr).

LYKKEBORGEN AS is registered as a limited company in Trondheim, Trøndelag with organisation number 988455857. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 4.5m, divided into 1 shares. The company's stated purpose is: “Finansiering samt å gjøre seg interessert i andre selskaper, investering i aksjer og andeler og utleie av egeneide leiligheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 971,000 in revenue and NOK −1.7m in operating profit.

Key figures · 2024

Revenue
NOK 971,000
Operating profit
NOK −1.7m
Equity
NOK 145.3m
Est. value
NOK 138.3m

Financial health · 2024

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

Who owns LYKKEBORGEN AS?

IVAR EDVARD LYKKE
LYKKEBORGEN AS
NOK 971,000 rev. · NOK −1.7m profit

LYKKEBORGEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LYKKEBORGEN AS own?

LYKKEBORGEN AS holds stakes in 9 companies:

See the full ownership structure →

Frequently asked questions about LYKKEBORGEN AS

Who owns LYKKEBORGEN AS?

IVAR EDVARD LYKKE is the largest registered owner, with 100.0%.

What is the revenue of LYKKEBORGEN AS?

LYKKEBORGEN AS had revenue of NOK 971,000 in 2024.

Where is LYKKEBORGEN AS based?

LYKKEBORGEN 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.