BIZTRAC BETA
Uoppgitt

OLFA HOLDING AS

Org. no. 889228172 Limited company (AS) Trondheim Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −26,000
Equity NOK 4.2m
Incorporated 2005
Share capital NOK 1.7m

Signals

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

OLFA HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 889228172. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2005. Registered share capital is NOK 1.7m, divided into 3789 shares. The company's stated purpose is: “Selv, eller ved deltakelse i, eller i samarbeid med andre selskaper, å investere i aksjer, eiendom eller dertil hørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −26,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −26,000
Equity
NOK 4.2m
Est. value
NOK 332.5m

Financial health · 2024

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

Who owns OLFA HOLDING AS?

EIVIND FALLAN
OLFA HOLDING AS
NOK 0 rev. · NOK −26,000 profit

OLFA HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does OLFA HOLDING AS own?

OLFA HOLDING AS holds stakes in 17 companies:

See the full ownership structure →

Frequently asked questions about OLFA HOLDING AS

Who owns OLFA HOLDING AS?

EIVIND FALLAN is the largest registered owner, with 54.4%.

What is the revenue of OLFA HOLDING AS?

OLFA HOLDING AS had revenue of NOK 0 in 2024.

Who is the general manager of OLFA HOLDING AS?

Eivind Fallan is registered as general manager of OLFA HOLDING AS.

Where is OLFA HOLDING AS based?

OLFA HOLDING AS has its business address in Trondheim.

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.