BIZTRAC BETA
Uoppgitt

ASLAK LUDVIGSEN HOLDING AS

Org. no. 934748557 Limited company (AS) Melhus Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −15,000
Equity NOK 9,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

ASLAK LUDVIGSEN HOLDING AS is registered as a limited company in Melhus, Trøndelag with organisation number 934748557. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investeringer i aksjer og eierandeler.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −15,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −15,000
Equity
NOK 9,000
Est. value
NOK 10,000

Financial health · 2025

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

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

Who owns ASLAK LUDVIGSEN HOLDING AS?

ASLAK LUDVIGSEN
ASLAK LUDVIGSEN HOLDING AS
NOK 0 rev. · NOK −15,000 profit

ASLAK LUDVIGSEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ASLAK LUDVIGSEN HOLDING AS own?

ASLAK LUDVIGSEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ASLAK LUDVIGSEN HOLDING AS

Who owns ASLAK LUDVIGSEN HOLDING AS?

ASLAK LUDVIGSEN is the largest registered owner, with 100.0%.

What is the revenue of ASLAK LUDVIGSEN HOLDING AS?

ASLAK LUDVIGSEN HOLDING AS had revenue of NOK 0 in 2025.

Where is ASLAK LUDVIGSEN HOLDING AS based?

ASLAK LUDVIGSEN HOLDING AS has its business address in Lundamo.

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.