biztrac. BETA
COMPANY REGISTER PROFILE
989245147 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other captive investment companies

LUKRIS INVEST AS

Org. no. 989245147 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −38,000
Equity NOK 38.9m
Incorporated 2005
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−38k kr).

LUKRIS INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 989245147. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i aksjer og andre verdipapirer og investering i og utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −38,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −38,000
▼ −2 %
Equity
NOK 38.9m
▲ +9 %
Est. value
NOK 32.9m

Financial health · 2025

Liquidity
802.86
Very good
Current assets ÷ current liabilities
Profitability
13.0%
Good
Return on total assets
Solidity
99.9%
Very good
Equity as a share of total capital

Who owns LUKRIS INVEST AS?

LUKRIS INVEST AS
NOK 0 rev. · NOK −38,000 profit

LUKRIS INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does LUKRIS INVEST AS own?

LUKRIS INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LUKRIS INVEST AS

Who owns LUKRIS INVEST AS?

Knut Balchen is the largest registered owner, with 50.0%.

What is the revenue of LUKRIS INVEST AS?

LUKRIS INVEST AS had revenue of NOK 0 in 2025.

Where is LUKRIS INVEST AS based?

LUKRIS INVEST AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.