BIZTRAC BETA
Uoppgitt

VESTFJORDEN ENTREPRENØR AS

Org. no. 913623444 Limited company (AS) Bærum Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 160,000
Operating profit NOK 102,000
Equity NOK 999,000
Incorporated 2014
Share capital NOK 50,000

Signals

1 flags
  • Nylig endring 2026-06-19 Adresseendring registrert 2026-06-19.

VESTFJORDEN ENTREPRENØR AS is registered as a limited company in Bærum, Akershus with organisation number 913623444. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2014. Registered share capital is NOK 50,000, divided into 500 shares. The company's stated purpose is: “Investering i verdipapirer og investeringsobjekter.”. The most recent filed accounts, for the 2025 financial year, show NOK 160,000 in revenue and NOK 102,000 in operating profit.

Key figures · 2025

Revenue
NOK 160,000
Operating profit
NOK 102,000
Equity
NOK 999,000
Est. value
NOK 899,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 VESTFJORDEN ENTREPRENØR AS?

FRODE PER BORGUND
VESTFJORDEN ENTREPRENØR AS
NOK 160,000 rev. · NOK 102,000 profit

VESTFJORDEN ENTREPRENØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VESTFJORDEN ENTREPRENØR AS

Who owns VESTFJORDEN ENTREPRENØR AS?

FRODE PER BORGUND is the largest registered owner, with 100.0%.

What is the revenue of VESTFJORDEN ENTREPRENØR AS?

VESTFJORDEN ENTREPRENØR AS had revenue of NOK 160,000 in 2025.

Who is the general manager of VESTFJORDEN ENTREPRENØR AS?

Frode Per Borgund is registered as general manager of VESTFJORDEN ENTREPRENØR AS.

Where is VESTFJORDEN ENTREPRENØR AS based?

VESTFJORDEN ENTREPRENØR AS has its business address in Blommenholm.

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.