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

FISKUM HOLDING AS

Org. no. 989015257 Limited company (AS) Øvre Eiker Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −155,000
Equity NOK 12.6m
Incorporated 2005
Share capital NOK 761,000

Signals

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

FISKUM HOLDING AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 989015257. The business is classified under rental and leasing of construction and civil engineering machinery and equipment (NACE 77.320). The company was incorporated in 2005. Registered share capital is NOK 761,000, divided into 1268 shares. The company's stated purpose is: “Investere i andre virksomheter gjennom aksjer eller på annen måte, samt virksomhet som naturlig faller inn under dette.”.

Key figures · 2024

Operating profit
NOK −155,000
Equity
NOK 12.6m
Est. value
NOK 21.2m

Financial health · 2024

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

Who owns FISKUM HOLDING AS?

TORE SVENSKERUD
FISKUM HOLDING AS
· NOK −155,000 profit

FISKUM HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does FISKUM HOLDING AS own?

FISKUM HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Group structure

FISKUM HOLDING AS er morselskap for 1 datterselskap:

Frequently asked questions about FISKUM HOLDING AS

Who owns FISKUM HOLDING AS?

TORE SVENSKERUD is the largest registered owner, with 70.0%.

Who is the general manager of FISKUM HOLDING AS?

Tore Svenskerud is registered as general manager of FISKUM HOLDING AS.

Where is FISKUM HOLDING AS based?

FISKUM HOLDING AS has its business address in Fiskum.

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.