BIZTRAC BETA
Business and other management consultancy activities

TRYM ABRAHAMSEN HOLDING AS

Org. no. 920384870 Limited company (AS) Molde Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK 68,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5k kr).

TRYM ABRAHAMSEN HOLDING AS is registered as a limited company in Molde, Møre og Romsdal with organisation number 920384870. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Investering og deltakelse i andre selskaper samt det som naturlig står i forbindelse med dette. Investering i eiendom, aksjer, obligasjoner og andre finansielle instrumenter samt det som naturlig står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −5,000
Equity
NOK 68,000
Est. value
NOK 111,000

Financial health · 2025

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

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

Who owns TRYM ABRAHAMSEN HOLDING AS?

TRYM OLAV ABRAHAMSEN
TRYM ABRAHAMSEN HOLDING AS
· NOK −5,000 profit

TRYM ABRAHAMSEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TRYM ABRAHAMSEN HOLDING AS own?

TRYM ABRAHAMSEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TRYM ABRAHAMSEN HOLDING AS

Who owns TRYM ABRAHAMSEN HOLDING AS?

TRYM OLAV ABRAHAMSEN is the largest registered owner, with 100.0%.

Where is TRYM ABRAHAMSEN HOLDING AS based?

TRYM ABRAHAMSEN HOLDING AS has its business address in Molde.

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.