biztrac. BETA
COMPANY REGISTER PROFILE
989255533 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

TIKA AS

Org. no. 989255533 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −3.8m
Equity NOK 62.7m
Incorporated 2005
Share capital NOK 83,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−3,8 mill kr).

TIKA AS is registered as a limited company in Oslo, Oslo with organisation number 989255533. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 83,000, divided into 100000 shares. The company's stated purpose is: “Investering i aksjer, investeringer i andre selskaper og annen økonomisk aktivitet, og investering i fast eiendom samt utleie av egen og leid eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −3.8m in operating profit.

Former names: BÅRD HAGA INVEST AS

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −3.8m
▼ −373 %
Equity
NOK 62.7m
▼ −4 %
Est. value
NOK 54.6m

Financial health · 2025

Liquidity
5.73
Very good
Current assets ÷ current liabilities
Profitability
4.9%
Weak
Return on total assets
Solidity
45.6%
Very good
Equity as a share of total capital

Who owns TIKA AS?

TIKA AS
NOK 0 rev. · NOK −3.8m profit

TIKA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TIKA AS own?

TIKA AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about TIKA AS

Who owns TIKA AS?

Bård Arnstein Haga is the largest registered owner, with 100.0%.

What is the revenue of TIKA AS?

TIKA AS had revenue of NOK 0 in 2025.

Where is TIKA AS based?

TIKA AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.