BIZTRAC BETA
Rental and operating of own or leased real estate

TYRA HOLDING AS

Org. no. 925626848 Limited company (AS) Frogn Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −29,000
Equity NOK 12.4m
Incorporated 2020
Share capital NOK 52,000

Signals

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

TYRA HOLDING AS is registered as a limited company in Frogn, Akershus with organisation number 925626848. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 52,000, divided into 20 shares. The company's stated purpose is: “Å være et investeringsselskap, herunder investeringer i aksjer, andeler i selskap, obligasjoner, fast eiendom, og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −29,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −29,000
Equity
NOK 12.4m
Est. value
NOK 21.9m

Financial health · 2025

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

Who owns TYRA HOLDING AS?

KJARTAN HAUGLUM
TYRA HOLDING AS
NOK 0 rev. · NOK −29,000 profit

TYRA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TYRA HOLDING AS own?

TYRA HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about TYRA HOLDING AS

Who owns TYRA HOLDING AS?

KJARTAN HAUGLUM is the largest registered owner, with 100.0%.

What is the revenue of TYRA HOLDING AS?

TYRA HOLDING AS had revenue of NOK 0 in 2025.

Where is TYRA HOLDING AS based?

TYRA HOLDING AS has its business address in Drøbak.

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.