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

TRYPRO AS

Org. no. 928611841 Limited company (AS) Asker Incorporated 2022 Active
Revenue 2025 NOK 1.9m
Operating profit NOK −827,000
Equity NOK −1.9m
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,9 mill kr).

TRYPRO AS is registered as a limited company in Asker, Akershus with organisation number 928611841. 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: “Entreprenør og rådgivningstjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK −827,000 in operating profit.

Former names: ESAS NEWCO 22005 AS

Key figures · 2025

Revenue
NOK 1.9m
▼ −16 %
Operating profit
NOK −827,000
▼ −219 %
Equity
NOK −1.9m
▼ −76 %

Financial health · 2025

Liquidity
2.59
Very good
Current assets ÷ current liabilities
Profitability
-53.8%
Not satisfactory
Return on total assets
Solidity
-117.8%
Weak
Equity as a share of total capital

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

Who owns TRYPRO AS?

TRYPRO AS
NOK 1.9m rev. · NOK −827,000 profit

TRYPRO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRYPRO AS

Who owns TRYPRO AS?

TRYPRO HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of TRYPRO AS?

TRYPRO AS had revenue of NOK 1.9m in 2025.

Who is the general manager of TRYPRO AS?

Øyvind Trydal is registered as general manager of TRYPRO AS.

Where is TRYPRO AS based?

TRYPRO AS has its business address in Asker.

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.