BIZTRAC BETA
Uoppgitt

M LANGVIK HOLDING AS

Org. no. 929354249 Limited company (AS) Halden Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 36,000
Operating profit NOK 19,000
Equity NOK 68,000
Incorporated 2022
Share capital NOK 30,000

M LANGVIK HOLDING AS is registered as a limited company in Halden, Østfold with organisation number 929354249. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drift og eierskap av andre aksjeselskap, samt konsulenttjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 36,000 in revenue and NOK 19,000 in operating profit.

Key figures · 2024

Revenue
NOK 36,000
Operating profit
NOK 19,000
Equity
NOK 68,000
Est. value
NOK 101,000

Financial health · 2024

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

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

Who owns M LANGVIK HOLDING AS?

MELVIN LANGVIK
M LANGVIK HOLDING AS
NOK 36,000 rev. · NOK 19,000 profit

M LANGVIK HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does M LANGVIK HOLDING AS own?

M LANGVIK HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about M LANGVIK HOLDING AS

Who owns M LANGVIK HOLDING AS?

MELVIN LANGVIK is the largest registered owner, with 50.0%.

What is the revenue of M LANGVIK HOLDING AS?

M LANGVIK HOLDING AS had revenue of NOK 36,000 in 2024.

Who is the general manager of M LANGVIK HOLDING AS?

Melvin Langvik is registered as general manager of M LANGVIK HOLDING AS.

Where is M LANGVIK HOLDING AS based?

M LANGVIK HOLDING AS has its business address in Halden.

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.