BIZTRAC BETA
Uoppgitt

BENTSEN INVEST AS

Org. no. 923267921 Limited company (AS) Kristiansand Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −13,000
Equity NOK 302,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

BENTSEN INVEST AS is registered as a limited company in Kristiansand, Agder with organisation number 923267921. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Selskapets virksomhet er formuesforvaltning, herunder investering i verdipapirer og andre formuesobjekter, samt kjøp og salg av verdipapirer og annen virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −13,000
Equity
NOK 302,000
Est. value
NOK 355,000

Financial health · 2025

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

Who owns BENTSEN INVEST AS?

SVEN BENTSEN
BENTSEN INVEST AS
NOK 0 rev. · NOK −13,000 profit

BENTSEN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BENTSEN INVEST AS own?

BENTSEN INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BENTSEN INVEST AS

Who owns BENTSEN INVEST AS?

SVEN BENTSEN is the largest registered owner, with 100.0%.

What is the revenue of BENTSEN INVEST AS?

BENTSEN INVEST AS had revenue of NOK 0 in 2025.

Where is BENTSEN INVEST AS based?

BENTSEN INVEST AS has its business address in Kristiansand S.

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.