BIZTRAC BETA
Uoppgitt

HOLDING ESPENS AS

Org. no. 929326059 Limited company (AS) Ringebu Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −17,000
Equity NOK 252,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

HOLDING ESPENS AS is registered as a limited company in Ringebu, Innlandet with organisation number 929326059. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investeringer i andre selskap, fast eiendom og det som har naturlig tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −17,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −17,000
Equity
NOK 252,000
Est. value
NOK 1.7m

Financial health · 2024

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

Who owns HOLDING ESPENS AS?

ESPEN NYLENDE
HOLDING ESPENS AS
NOK 0 rev. · NOK −17,000 profit

HOLDING ESPENS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HOLDING ESPENS AS own?

HOLDING ESPENS AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about HOLDING ESPENS AS

Who owns HOLDING ESPENS AS?

ESPEN NYLENDE is the largest registered owner, with 100.0%.

What is the revenue of HOLDING ESPENS AS?

HOLDING ESPENS AS had revenue of NOK 0 in 2024.

Who is the general manager of HOLDING ESPENS AS?

Espen Nylende is registered as general manager of HOLDING ESPENS AS.

Where is HOLDING ESPENS AS based?

HOLDING ESPENS AS has its business address in Fåvang.

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.