biztrac. BETA
COMPANY REGISTER PROFILE
929634896 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Business and other management consultancy activities

NORINDTRY AS

Org. no. 929634896 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 168,000
Operating profit NOK 75,000
Equity NOK 35,000
Incorporated 2022
Share capital NOK 30,000

NORINDTRY AS is registered as a limited company in Oslo, Oslo with organisation number 929634896. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Management consulting/bedriftsrådgivning, forvaltning av investeringer og eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 168,000 in revenue and NOK 75,000 in operating profit.

Former names: TRYTI AS

Key figures · 2025

Revenue
NOK 168,000
Operating profit
NOK 75,000
▲ +519 %
Equity
NOK 35,000
▲ +364 %
Est. value
NOK 193,000

Financial health · 2025

Liquidity
7.19
Very good
Current assets ÷ current liabilities
Profitability
9.8%
Satisfactory
Return on total assets
Solidity
4.3%
Weak
Equity as a share of total capital

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

Who owns NORINDTRY AS?

NORINDTRY AS
NOK 168,000 rev. · NOK 75,000 profit

NORINDTRY AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NORINDTRY AS own?

NORINDTRY AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about NORINDTRY AS

Who owns NORINDTRY AS?

Helge Asbjørn Tryti is the largest registered owner, with 100.0%.

What is the revenue of NORINDTRY AS?

NORINDTRY AS had revenue of NOK 168,000 in 2025.

Where is NORINDTRY AS based?

NORINDTRY 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.