BIZTRAC BETA
Development of building projects

TORVIK JENSEN AS

Org. no. 988872733 Limited company (AS) Larvik Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −278,000
Equity NOK 8.5m
Incorporated 2005
Share capital NOK 300,000

Signals

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

TORVIK JENSEN AS is registered as a limited company in Larvik, Vestfold with organisation number 988872733. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2005. Registered share capital is NOK 300,000, divided into 300000 shares. The company's stated purpose is: “Forvaltning og utvikling av eiendommer, taksering av bolig og næringseiendommer og rådgivende ingeniørvirksomhet, samt hva hermed står i forbindelse, herunder også deltakelse i andre selskaper. Selskapets virksomhet er også å eie andre aksjer og verdipapirer.”.

Key figures · 2025

Operating profit
NOK −278,000
Equity
NOK 8.5m
Est. value
NOK 7.1m

Financial health · 2025

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

Who owns TORVIK JENSEN AS?

HARALD CHRISTIAN TORVIK JENSEN
TORVIK JENSEN AS
· NOK −278,000 profit

TORVIK JENSEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TORVIK JENSEN AS own?

TORVIK JENSEN AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about TORVIK JENSEN AS

Who owns TORVIK JENSEN AS?

HARALD CHRISTIAN TORVIK JENSEN is the largest registered owner, with 100.0%.

Who is the general manager of TORVIK JENSEN AS?

Harald Christian Torvik Jensen is registered as general manager of TORVIK JENSEN AS.

Where is TORVIK JENSEN AS based?

TORVIK JENSEN AS has its business address in Tjodalyng.

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.