BIZTRAC BETA
Other captive investment companies

TJENSSEN AS

Org. no. 917573603 Limited company (AS) Alver Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 159,000
Operating profit NOK −1.0m
Equity NOK 44.7m
Incorporated 2016
Share capital NOK 135,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,0 mill kr).

TJENSSEN AS is registered as a limited company in Alver, Vestland with organisation number 917573603. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2016. Registered share capital is NOK 135,000, divided into 45000 shares. The company's stated purpose is: “Å investere i aksjer og andeler, eiendom, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 159,000 in revenue and NOK −1.0m in operating profit.

Key figures · 2025

Revenue
NOK 159,000
Operating profit
NOK −1.0m
Equity
NOK 44.7m
Est. value
NOK 24.6m

Financial health · 2025

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

Who owns TJENSSEN AS?

THORBJØRN JENSSEN
TJENSSEN AS
NOK 159,000 rev. · NOK −1.0m profit

TJENSSEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TJENSSEN AS own?

TJENSSEN AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about TJENSSEN AS

Who owns TJENSSEN AS?

THORBJØRN JENSSEN is the largest registered owner, with 100.0%.

What is the revenue of TJENSSEN AS?

TJENSSEN AS had revenue of NOK 159,000 in 2025.

Who is the general manager of TJENSSEN AS?

Thorbjørn Jenssen is registered as general manager of TJENSSEN AS.

Where is TJENSSEN AS based?

TJENSSEN AS has its business address in Frekhaug.

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.