BIZTRAC BETA
Other captive investment companies

HOSETH INVEST AS

Org. no. 919912006 Limited company (AS) Drammen Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 196,000
Operating profit NOK 182,000
Equity NOK 2.8m
Incorporated 2017
Share capital NOK 30,000

HOSETH INVEST AS is registered as a limited company in Drammen, Buskerud with organisation number 919912006. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Eie aksjer og andeler i andre selskaper. Selskapet har også anledning til å drive med investering og utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 196,000 in revenue and NOK 182,000 in operating profit.

Key figures · 2025

Revenue
NOK 196,000
Operating profit
NOK 182,000
Equity
NOK 2.8m
Est. value
NOK 2.1m

Financial health · 2025

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

Who owns HOSETH INVEST AS?

VIDAR HOSETH
HOSETH INVEST AS
NOK 196,000 rev. · NOK 182,000 profit

HOSETH INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HOSETH INVEST AS own?

HOSETH INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HOSETH INVEST AS

Who owns HOSETH INVEST AS?

VIDAR HOSETH is the largest registered owner, with 100.0%.

What is the revenue of HOSETH INVEST AS?

HOSETH INVEST AS had revenue of NOK 196,000 in 2025.

Who is the general manager of HOSETH INVEST AS?

Vidar Hoseth is registered as general manager of HOSETH INVEST AS.

Where is HOSETH INVEST AS based?

HOSETH INVEST 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.