BIZTRAC BETA
Uoppgitt

LARS EIKEFJORD HOLDING AS

Org. no. 892009562 Limited company (AS) Bærum Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −980,000
Equity NOK 21.0m
Incorporated 2007
Share capital NOK 100,000

Signals

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

LARS EIKEFJORD HOLDING AS is registered as a limited company in Bærum, Akershus with organisation number 892009562. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investeringer i aksjer, verdipapirer og fast eiendom, samt alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −980,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −980,000
Equity
NOK 21.0m
Est. value
NOK 24.6m

Financial health · 2025

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

Who owns LARS EIKEFJORD HOLDING AS?

LARS EIKEFJORD
LARS EIKEFJORD HOLDING AS
NOK 0 rev. · NOK −980,000 profit

LARS EIKEFJORD HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LARS EIKEFJORD HOLDING AS own?

LARS EIKEFJORD HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about LARS EIKEFJORD HOLDING AS

Who owns LARS EIKEFJORD HOLDING AS?

LARS EIKEFJORD is the largest registered owner, with 100.0%.

What is the revenue of LARS EIKEFJORD HOLDING AS?

LARS EIKEFJORD HOLDING AS had revenue of NOK 0 in 2025.

Where is LARS EIKEFJORD HOLDING AS based?

LARS EIKEFJORD HOLDING AS has its business address in Gjettum.

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.