BIZTRAC BETA
Uoppgitt

LEDAV 607 HOLDING AS

Org. no. 932821516 Limited company (AS) Fauske Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −6,000
Equity NOK 698,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

LEDAV 607 HOLDING AS is registered as a limited company in Fauske, Nordland with organisation number 932821516. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Erverve og eie aksjer og andeler i andre selskaper, handel i finansielle instrumenter samt all annen virksomhet som naturlig hører derved.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 698,000
Est. value
NOK 853,000

Financial health · 2024

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

Who owns LEDAV 607 HOLDING AS?

LEIF INGE DAVIK
LEDAV 607 HOLDING AS
NOK 0 rev. · NOK −6,000 profit

LEDAV 607 HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LEDAV 607 HOLDING AS own?

LEDAV 607 HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LEDAV 607 HOLDING AS

Who owns LEDAV 607 HOLDING AS?

LEIF INGE DAVIK is the largest registered owner, with 100.0%.

What is the revenue of LEDAV 607 HOLDING AS?

LEDAV 607 HOLDING AS had revenue of NOK 0 in 2024.

Where is LEDAV 607 HOLDING AS based?

LEDAV 607 HOLDING AS has its business address in Fauske.

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.