BIZTRAC BETA
Preventive health care activities

TRI-O AS

Org. no. 894516372 Limited company (AS) Oslo Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 279,000
Operating profit NOK 73,000
Equity NOK −54,000
Incorporated 2009
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−54k kr).

TRI-O AS is registered as a limited company in Oslo, Oslo with organisation number 894516372. The business is classified under preventive health care activities (NACE 86.992). The company was incorporated in 2009. Registered share capital is NOK 30,000, divided into 100000 shares. The company's stated purpose is: “Rådgivning innen helse- og personaltjenester, herunder deltagelse i andre selskaper eller samarbeid med andre innen samme område. Selskapet skal kunne investere i verdipapirer og fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 279,000 in revenue and NOK 73,000 in operating profit.

Key figures · 2024

Revenue
NOK 279,000
Operating profit
NOK 73,000
Equity
NOK −54,000
Est. value
NOK 406,000

Financial health · 2024

Liquidity
0.66
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-51.0%
Weak
Equity as a share of total capital

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

Who owns TRI-O AS?

OLA NIELSSØNN EBBESEN
TRI-O AS
NOK 279,000 rev. · NOK 73,000 profit

TRI-O AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRI-O AS

Who owns TRI-O AS?

OLA NIELSSØNN EBBESEN is the largest registered owner, with 100.0%.

What is the revenue of TRI-O AS?

TRI-O AS had revenue of NOK 279,000 in 2024.

Who is the general manager of TRI-O AS?

Ola Nielssønn Ebbesen is registered as general manager of TRI-O AS.

Where is TRI-O AS based?

TRI-O 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 15.06.2026.

Report a problem

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