BIZTRAC BETA
Uoppgitt

FIMBUL HOLDING AS

Org. no. 932094533 Limited company (AS) Oppdal Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 152,000
Operating profit NOK −706,000
Equity NOK 5.4m
Incorporated 2023
Share capital NOK 30,000

Signals

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

FIMBUL HOLDING AS is registered as a limited company in Oppdal, Trøndelag with organisation number 932094533. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investere i aksjer og andeler i selskaper og aktiviteter som derved hører til.”. The most recent filed accounts, for the 2025 financial year, show NOK 152,000 in revenue and NOK −706,000 in operating profit.

Key figures · 2025

Revenue
NOK 152,000
Operating profit
NOK −706,000
Equity
NOK 5.4m
Est. value
NOK 9.4m

Financial health · 2025

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

Who owns FIMBUL HOLDING AS?

TROND AALDE
FIMBUL HOLDING AS
NOK 152,000 rev. · NOK −706,000 profit

FIMBUL HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FIMBUL HOLDING AS own?

FIMBUL HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FIMBUL HOLDING AS

Who owns FIMBUL HOLDING AS?

TROND AALDE is the largest registered owner, with 100.0%.

What is the revenue of FIMBUL HOLDING AS?

FIMBUL HOLDING AS had revenue of NOK 152,000 in 2025.

Who is the general manager of FIMBUL HOLDING AS?

Trond Aalde is registered as general manager of FIMBUL HOLDING AS.

Where is FIMBUL HOLDING AS based?

FIMBUL HOLDING AS has its business address in Oppdal.

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.