BIZTRAC BETA
Rental and leasing of construction and civil engineering machinery and equipment

E. BREDESEN INVEST AS

Org. no. 926086626 Limited company (AS) Sunndal Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −10,000
Equity NOK 5.5m
Incorporated 2020
Share capital NOK 30,000

Signals

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

E. BREDESEN INVEST AS is registered as a limited company in Sunndal, Møre og Romsdal with organisation number 926086626. The business is classified under rental and leasing of construction and civil engineering machinery and equipment (NACE 77.320). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Å eie aksjer og andeler, kapital samt alt som står i den forbindelse.”.

Key figures · 2024

Operating profit
NOK −10,000
Equity
NOK 5.5m
Est. value
NOK 15.6m

Financial health · 2024

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

Who owns E. BREDESEN INVEST AS?

ERIK BREDESEN
E. BREDESEN INVEST AS
· NOK −10,000 profit

E. BREDESEN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does E. BREDESEN INVEST AS own?

E. BREDESEN INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

E. BREDESEN INVEST AS er morselskap for 1 datterselskap:

Frequently asked questions about E. BREDESEN INVEST AS

Who owns E. BREDESEN INVEST AS?

ERIK BREDESEN is the largest registered owner, with 100.0%.

Who is the general manager of E. BREDESEN INVEST AS?

Erik Bredesen is registered as general manager of E. BREDESEN INVEST AS.

Where is E. BREDESEN INVEST AS based?

E. BREDESEN INVEST AS has its business address in Grøa.

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.