biztrac. BETA
COMPANY REGISTER PROFILE
927009706 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Activities of advertising agencies

TRY HOLDING AS

Org. no. 927009706 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 5.7m
Operating profit NOK 5.6m
Equity NOK 434.8m
Incorporated 2021
Share capital NOK 15.1m

TRY HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 927009706. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2021. Registered share capital is NOK 15.1m, divided into 30000 shares. The company's stated purpose is: “Å være et investeringsselskap, herunder å investere i aksjer, obligasjoner, andeler i selskap etter selskapsloven og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.7m in revenue and NOK 5.6m in operating profit.

Former names: FC HOLDING XIII AS

Key figures · 2025

Revenue
NOK 5.7m
▼ −69 %
Operating profit
NOK 5.6m
▼ −70 %
Equity
NOK 434.8m
▲ +2 %
Est. value
NOK 251.6m

Financial health · 2025

Liquidity
12.26
Very good
Current assets ÷ current liabilities
Profitability
1.6%
Weak
Return on total assets
Solidity
99.7%
Very good
Equity as a share of total capital

Who owns TRY HOLDING AS?

TRY HOLDING AS
NOK 5.7m rev. · NOK 5.6m profit

TRY HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TRY HOLDING AS own?

TRY HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about TRY HOLDING AS

Who owns TRY HOLDING AS?

FERD VEKSTPARTNER AS is the largest registered owner, with 100.0%.

What is the revenue of TRY HOLDING AS?

TRY HOLDING AS had revenue of NOK 5.7m in 2025.

Where is TRY HOLDING AS based?

TRY HOLDING 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.