BIZTRAC BETA
Intermediation service activities for non-specialised retail sale

BENGTSEN HOLDING AS

Org. no. 989216600 Limited company (AS) Verdal Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −307,000
Equity NOK 21.2m
Incorporated 2005
Share capital NOK 100,000

Signals

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

BENGTSEN HOLDING AS is registered as a limited company in Verdal, Trøndelag with organisation number 989216600. The business is classified under intermediation service activities for non-specialised retail sale (NACE 47.910). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Selskapets virksomhet er kjøp og salg av aksjer, kjøp og salg av eiendom og annen virksomhet som står i naturlig forbindelse med dette, herunder å delta i andre selskap med lignende virksomhet.”.

Key figures · 2024

Operating profit
NOK −307,000
Equity
NOK 21.2m
Est. value
NOK 15.4m

Financial health · 2025

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

Who owns BENGTSEN HOLDING AS?

JAN IVAN BENGTSEN
BENGTSEN HOLDING AS
· NOK −307,000 profit

BENGTSEN HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BENGTSEN HOLDING AS own?

BENGTSEN HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about BENGTSEN HOLDING AS

Who owns BENGTSEN HOLDING AS?

JAN IVAN BENGTSEN is the largest registered owner, with 80.0%.

Who is the general manager of BENGTSEN HOLDING AS?

Jan Ivan Bengtsen is registered as general manager of BENGTSEN HOLDING AS.

Where is BENGTSEN HOLDING AS based?

BENGTSEN HOLDING AS has its business address in Verdal.

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.