BIZTRAC BETA
Rental and operating of own or leased real estate

LYKKJA AS

Org. no. 986570373 Limited company (AS) Orkland Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 159,000
Operating profit NOK −456,000
Equity NOK 5.0m
Incorporated 2004
Share capital NOK 110,000

Signals

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

LYKKJA AS is registered as a limited company in Orkland, Trøndelag with organisation number 986570373. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2004. Registered share capital is NOK 110,000, divided into 1210 shares. The company's stated purpose is: “Utbygging, utleie og drift av fast eiendom, kjøp og slag av fast eiendom, samt hva herved står i forbindelse, heunder delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 159,000 in revenue and NOK −456,000 in operating profit.

Key figures · 2024

Revenue
NOK 159,000
Operating profit
NOK −456,000
Equity
NOK 5.0m
Est. value
NOK 3.6m

Financial health · 2023

Liquidity
-47.73
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.9%
Very good
Equity as a share of total capital

Who owns LYKKJA AS?

No shareholders are registered for LYKKJA AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Which companies does LYKKJA AS own?

LYKKJA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LYKKJA AS

What is the revenue of LYKKJA AS?

LYKKJA AS had revenue of NOK 159,000 in 2024.

Who is the general manager of LYKKJA AS?

Lillian Asbøll Opøyen is registered as general manager of LYKKJA AS.

Where is LYKKJA AS based?

LYKKJA AS has its business address in Svorkmo.

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.