biztrac. BETA
COMPANY REGISTER PROFILE
934231538 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Industrial product and fashion design activities

TYR7 HOLDING AS

Org. no. 934231538 Limited company (AS) Frogn Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 30,000
Incorporated 2024
Share capital NOK 30,000

TYR7 HOLDING AS is registered as a limited company in Frogn, Akershus with organisation number 934231538. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie aksjer og investere i virksomheter av enhver art, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 30,000
▲ +0 %
Est. value
NOK 49,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
0.0%
Not satisfactory
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

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

Who owns TYR7 HOLDING AS?

TYR7 HOLDING AS
NOK 0 rev. · NOK 0 profit

TYR7 HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TYR7 HOLDING AS own?

TYR7 HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TYR7 HOLDING AS

Who owns TYR7 HOLDING AS?

Alexander Michael Rafaelsen is the largest registered owner, with 100.0%.

What is the revenue of TYR7 HOLDING AS?

TYR7 HOLDING AS had revenue of NOK 0 in 2025.

Where is TYR7 HOLDING AS based?

TYR7 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 03.10.2026.

Report a problem

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