BIZTRAC BETA
Other captive investment companies

TIGERBOY AS

Org. no. 997701011 Limited company (AS) Bærum Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −55,000
Equity NOK 29.7m
Incorporated 2011
Share capital NOK 24.4m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−55k kr).

TIGERBOY AS is registered as a limited company in Bærum, Akershus with organisation number 997701011. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2011. Registered share capital is NOK 24.4m, divided into 24400000 shares. The company's stated purpose is: “Investeringsselskap, herunder delta i andre selskaper med samme formål og investere i aksjer, fonds- og selskapsandeler og andre finansielle instrumenter, samt å utøve slik annen virksomhet som naturlig henger sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −55,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −55,000
Equity
NOK 29.7m
Est. value
NOK 27.1m

Financial health · 2024

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

Who owns TIGERBOY AS?

PETER ULRIK HAMMERICH
TIGERBOY AS
NOK 0 rev. · NOK −55,000 profit

TIGERBOY AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TIGERBOY AS own?

TIGERBOY AS holds stakes in 8 companies:

See the full ownership structure →

Frequently asked questions about TIGERBOY AS

Who owns TIGERBOY AS?

PETER ULRIK HAMMERICH is the largest registered owner, with 50.0%.

What is the revenue of TIGERBOY AS?

TIGERBOY AS had revenue of NOK 0 in 2024.

Where is TIGERBOY AS based?

TIGERBOY AS has its business address in Jar.

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.