BIZTRAC BETA
Uoppgitt

PER LANGDALEN HOLDING AS

Org. no. 932942623 Limited company (AS) Elverum Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −6,000
Equity NOK 177,000
Incorporated 2024
Share capital NOK 195,000

Signals

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

PER LANGDALEN HOLDING AS is registered as a limited company in Elverum, Innlandet with organisation number 932942623. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 195,000, divided into 650 shares. The company's stated purpose is: “Investeringer i aksjer og eiendom. Selskapet kan delta i andre selskaper med samme eller lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 177,000
Est. value
NOK 208,000

Financial health · 2025

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

Who owns PER LANGDALEN HOLDING AS?

PER LANGDALEN
PER LANGDALEN HOLDING AS
NOK 0 rev. · NOK −6,000 profit

PER LANGDALEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PER LANGDALEN HOLDING AS own?

PER LANGDALEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PER LANGDALEN HOLDING AS

Who owns PER LANGDALEN HOLDING AS?

PER LANGDALEN is the largest registered owner, with 100.0%.

What is the revenue of PER LANGDALEN HOLDING AS?

PER LANGDALEN HOLDING AS had revenue of NOK 0 in 2025.

Where is PER LANGDALEN HOLDING AS based?

PER LANGDALEN HOLDING AS has its business address in Hernes.

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.