BIZTRAC BETA
Uoppgitt

JOSTEIN FOLKEDAL HOLDING AS

Org. no. 924460172 Limited company (AS) Drammen Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 1.2m
Incorporated 2020
Share capital NOK 1.2m

Signals

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

JOSTEIN FOLKEDAL HOLDING AS is registered as a limited company in Drammen, Buskerud with organisation number 924460172. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 1.2m, divided into 1250 shares. The company's stated purpose is: “Eie av aksjer i selskap samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 1.2m
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns JOSTEIN FOLKEDAL HOLDING AS?

JOSTEIN FOLKEDAL
JOSTEIN FOLKEDAL HOLDING AS
NOK 0 rev. · NOK −5,000 profit

JOSTEIN FOLKEDAL HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JOSTEIN FOLKEDAL HOLDING AS own?

JOSTEIN FOLKEDAL HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JOSTEIN FOLKEDAL HOLDING AS

Who owns JOSTEIN FOLKEDAL HOLDING AS?

JOSTEIN FOLKEDAL is the largest registered owner, with 100.0%.

What is the revenue of JOSTEIN FOLKEDAL HOLDING AS?

JOSTEIN FOLKEDAL HOLDING AS had revenue of NOK 0 in 2025.

Where is JOSTEIN FOLKEDAL HOLDING AS based?

JOSTEIN FOLKEDAL HOLDING AS has its business address in Drammen.

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.