BIZTRAC BETA
Uoppgitt

EIDE PEDERSEN HOLDING AS

Org. no. 928632652 Limited company (AS) Lillehammer Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −10,000
Equity NOK 13,000
Incorporated 2021
Share capital NOK 50,000

Signals

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

EIDE PEDERSEN HOLDING AS is registered as a limited company in Lillehammer, Innlandet with organisation number 928632652. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 50,000, divided into 1000 shares. The company's stated purpose is: “Investere i aksjer og eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

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

Financial health · 2025

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

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

Who owns EIDE PEDERSEN HOLDING AS?

BENDIX EIDE PEDERSEN
EIDE PEDERSEN HOLDING AS
NOK 0 rev. · NOK −10,000 profit

EIDE PEDERSEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EIDE PEDERSEN HOLDING AS own?

EIDE PEDERSEN HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about EIDE PEDERSEN HOLDING AS

Who owns EIDE PEDERSEN HOLDING AS?

BENDIX EIDE PEDERSEN is the largest registered owner, with 100.0%.

What is the revenue of EIDE PEDERSEN HOLDING AS?

EIDE PEDERSEN HOLDING AS had revenue of NOK 0 in 2025.

Where is EIDE PEDERSEN HOLDING AS based?

EIDE PEDERSEN HOLDING AS has its business address in Lillehammer.

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.