biztrac. BETA
COMPANY REGISTER PROFILE
931831984 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Sports activities n.e.c.

TRIO HOLDING AS

Org. no. 931831984 Limited company (AS) Rælingen Incorporated 2023 Active
Revenue 2025 NOK 1.2m
Operating profit NOK 225,000
Equity NOK 258,000
Incorporated 2023
Share capital NOK 30,000

TRIO HOLDING AS is registered as a limited company in Rælingen, Akershus with organisation number 931831984. The business is classified under sports activities n.e.c. (NACE 93.190). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Yte tjenester til eget foretak/konsern, samt drive med investeringer i selskaper, aksjer, eiendommer, forretningsbygg, fond og andre verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 225,000 in operating profit.

Former names: LILLESTRØM INDOOR GOLF AS

Key figures · 2025

Revenue
NOK 1.2m
▼ −2 %
Operating profit
NOK 225,000
▲ +73 %
Equity
NOK 258,000
▲ +158 %
Est. value
NOK 924,000

Financial health · 2025

Liquidity
0.54
Weak
Current assets ÷ current liabilities
Profitability
23.6%
Very good
Return on total assets
Solidity
24.6%
Good
Equity as a share of total capital

Who owns TRIO HOLDING AS?

TRIO HOLDING AS
NOK 1.2m rev. · NOK 225,000 profit

TRIO HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does TRIO HOLDING AS own?

TRIO HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TRIO HOLDING AS

Who owns TRIO HOLDING AS?

HEMACA HOLDING AS is the largest registered owner, with 33.3%.

What is the revenue of TRIO HOLDING AS?

TRIO HOLDING AS had revenue of NOK 1.2m in 2025.

Where is TRIO HOLDING AS based?

TRIO HOLDING AS has its business address in Fjerdingby.

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.