BIZTRAC BETA
Other captive investment companies

DINH INVEST AS

Org. no. 921498985 Limited company (AS) Frøya Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −23,000
Equity NOK 89,000
Incorporated 2018
Share capital NOK 650,000

Signals

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

DINH INVEST AS is registered as a limited company in Frøya, Trøndelag with organisation number 921498985. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2018. Registered share capital is NOK 650,000, divided into 650 shares. The company's stated purpose is: “Holding/investering i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −23,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −23,000
Equity
NOK 89,000
Est. value
NOK 82,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns DINH INVEST AS?

SON HUNG DINH
DINH INVEST AS
NOK 0 rev. · NOK −23,000 profit

DINH INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DINH INVEST AS own?

DINH INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about DINH INVEST AS

Who owns DINH INVEST AS?

SON HUNG DINH is the largest registered owner, with 100.0%.

What is the revenue of DINH INVEST AS?

DINH INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of DINH INVEST AS?

Son Hung Dinh is registered as general manager of DINH INVEST AS.

Where is DINH INVEST AS based?

DINH INVEST AS has its business address in Kverva.

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.