BIZTRAC BETA
COMPANY REGISTER PROFILE
933761959 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

LOMMEDALEN HOLDING AS

Org. no. 933761959 Limited company (AS) Asker Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −10,000
Equity NOK 80,000
Incorporated 2024
Share capital NOK 90,000

Signals

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

LOMMEDALEN HOLDING AS is registered as a limited company in Asker, Akershus with organisation number 933761959. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 90,000, divided into 90 shares. The company's stated purpose is: “Investering i andre selskaper, rådgivningstjenester innen bygg og anlegg og annet som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −10,000
Equity
NOK 80,000
Est. value
NOK 94,000

Financial health · 2024

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LOMMEDALEN HOLDING AS?

CHRISTIAN EINE STUDSRØD
LOMMEDALEN HOLDING AS
NOK 0 rev. · NOK −10,000 profit

LOMMEDALEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LOMMEDALEN HOLDING AS

Who owns LOMMEDALEN HOLDING AS?

CHRISTIAN EINE STUDSRØD is the largest registered owner, with 100.0%.

What is the revenue of LOMMEDALEN HOLDING AS?

LOMMEDALEN HOLDING AS had revenue of NOK 0 in 2024.

Where is LOMMEDALEN HOLDING AS based?

LOMMEDALEN HOLDING AS has its business address in Asker.

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.