BIZTRAC BETA
Plumbing installation

PÅL TRY AS

Org. no. 989029657 Limited company (AS) Kristiansand Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 116,000
Operating profit NOK −55,000
Equity NOK 7.0m
Incorporated 2005
Share capital NOK 182,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−55k kr).

PÅL TRY AS is registered as a limited company in Kristiansand, Agder with organisation number 989029657. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2005. Registered share capital is NOK 182,000, divided into 182000 shares. The company's stated purpose is: “Investere i, eie og selge aksjer og selskapsandeler i andre virksomheter, samt konsulentvirksomhet og annet som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 116,000 in revenue and NOK −55,000 in operating profit.

Key figures · 2024

Revenue
NOK 116,000
Operating profit
NOK −55,000
Equity
NOK 7.0m
Est. value
NOK 7.1m

Financial health · 2024

Liquidity
11.18
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
91.3%
Very good
Equity as a share of total capital

Who owns PÅL TRY AS?

PÅL VETLE TRY
PÅL TRY AS
NOK 116,000 rev. · NOK −55,000 profit

PÅL TRY AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PÅL TRY AS own?

PÅL TRY AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about PÅL TRY AS

Who owns PÅL TRY AS?

PÅL VETLE TRY is the largest registered owner, with 100.0%.

What is the revenue of PÅL TRY AS?

PÅL TRY AS had revenue of NOK 116,000 in 2024.

Who is the general manager of PÅL TRY AS?

Pål Vetle Try is registered as general manager of PÅL TRY AS.

Where is PÅL TRY AS based?

PÅL TRY AS has its business address in Søgne.

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.