BIZTRAC BETA
Other captive investment companies

ONKEL TOR AS

Org. no. 914720281 Limited company (AS) Bærum Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 1,000
Operating profit NOK −52,000
Equity NOK 45,000
Incorporated 2014
Share capital NOK 30,000

Signals

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

ONKEL TOR AS is registered as a limited company in Bærum, Akershus with organisation number 914720281. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investeringer i aksjer og andre verdipapirer, og dertil tilhørende virksomhet. Selskapet kan ha eierandeler i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 1,000 in revenue and NOK −52,000 in operating profit.

Key figures · 2025

Revenue
NOK 1,000
Operating profit
NOK −52,000
Equity
NOK 45,000
Est. value
NOK 25,000

Financial health · 2025

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

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

Who owns ONKEL TOR AS?

ANDREAS TERJE RØNNING HAGEN
ONKEL TOR AS
NOK 1,000 rev. · NOK −52,000 profit

ONKEL TOR AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ONKEL TOR AS own?

ONKEL TOR AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about ONKEL TOR AS

Who owns ONKEL TOR AS?

ANDREAS TERJE RØNNING HAGEN is the largest registered owner, with 50.0%.

What is the revenue of ONKEL TOR AS?

ONKEL TOR AS had revenue of NOK 1,000 in 2025.

Where is ONKEL TOR AS based?

ONKEL TOR AS has its business address in Bekkestua.

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.