BIZTRAC BETA
Rental and operating of own or leased real estate

THIMA INVEST AS

Org. no. 922321876 Limited company (AS) Austevoll Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −2,000
Equity NOK −6,000
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−6k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2k kr).

THIMA INVEST AS is registered as a limited company in Austevoll, Vestland with organisation number 922321876. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Å investere i eiendom, aksjer og andre verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK −6,000

Financial health · 2025

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

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

Who owns THIMA INVEST AS?

THOR INGE DALSEIDE
THIMA INVEST AS
NOK 0 rev. · NOK −2,000 profit

THIMA INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does THIMA INVEST AS own?

THIMA INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about THIMA INVEST AS

Who owns THIMA INVEST AS?

THOR INGE DALSEIDE is the largest registered owner, with 100.0%.

What is the revenue of THIMA INVEST AS?

THIMA INVEST AS had revenue of NOK 0 in 2025.

Where is THIMA INVEST AS based?

THIMA INVEST AS has its business address in Torangsvåg.

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.