BIZTRAC BETA
COMPANY REGISTER PROFILE
988986011 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

TØRØ HOLDING AS

Org. no. 988986011 Limited company (AS) Skaun Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 323,000
Operating profit NOK 90,000
Equity NOK 28.8m
Incorporated 2005
Share capital NOK 214,000

TØRØ HOLDING AS is registered as a limited company in Skaun, Trøndelag with organisation number 988986011. 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 214,000, divided into 2143 shares. The company's stated purpose is: “Kjøp og salg av aksjer og fast eiendom og hva hermed står i forbindelse, herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 323,000 in revenue and NOK 90,000 in operating profit.

Key figures · 2025

Revenue
NOK 323,000
▼ −1 %
Operating profit
NOK 90,000
▲ +175 %
Equity
NOK 28.8m
▼ −18 %
Est. value
NOK 20.0m

Financial health · 2025

Liquidity
19.19
Very good
Current assets ÷ current liabilities
Profitability
3.0%
Weak
Return on total assets
Solidity
96.9%
Very good
Equity as a share of total capital

Who owns TØRØ HOLDING AS?

TØRØ HOLDING AS
NOK 323,000 rev. · NOK 90,000 profit

TØRØ HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TØRØ HOLDING AS own?

TØRØ HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TØRØ HOLDING AS

Who owns TØRØ HOLDING AS?

MARIT EIDSKREM TØRØ is the largest registered owner, with 70.0%.

What is the revenue of TØRØ HOLDING AS?

TØRØ HOLDING AS had revenue of NOK 323,000 in 2025.

Where is TØRØ HOLDING AS based?

TØRØ HOLDING AS has its business address in Buvika.

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

Report a problem

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