BIZTRAC BETA
Uoppgitt

TOR HATLEN INVEST AS

Org. no. 934921763 Limited company (AS) Trondheim Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −13
Equity NOK −2,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

TOR HATLEN INVEST AS is registered as a limited company in Trondheim, Trøndelag with organisation number 934921763. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Eie aksjer og andeler i andre virksomheter, samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −13 in operating profit.

Key figures · 2025

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

Financial health · 2025

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

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

Who owns TOR HATLEN INVEST AS?

Tor Hatlen
TOR HATLEN INVEST AS
NOK 0 rev. · NOK −13 profit

TOR HATLEN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TOR HATLEN INVEST AS own?

TOR HATLEN INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TOR HATLEN INVEST AS

Who owns TOR HATLEN INVEST AS?

Tor Hatlen is the largest registered owner, with 100.0%.

What is the revenue of TOR HATLEN INVEST AS?

TOR HATLEN INVEST AS had revenue of NOK 0 in 2025.

Where is TOR HATLEN INVEST AS based?

TOR HATLEN INVEST AS has its business address in Tiller.

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.