BIZTRAC BETA
COMPANY REGISTER PROFILE
816122562 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Other captive investment companies

RENTECH AS

Org. no. 816122562 Limited company (AS) Bærum Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −54,000
Equity NOK 166,000
Incorporated 2015
Share capital NOK 30,000

Signals

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

RENTECH AS is registered as a limited company in Bærum, Akershus with organisation number 816122562. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Generell investeringsvirksomhet og konsulentvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −54,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −54,000
Equity
NOK 166,000
Est. value
NOK 152,000

Financial health · 2025

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

Who owns RENTECH AS?

PÅL RENLI
RENTECH AS
NOK 0 rev. · NOK −54,000 profit

RENTECH AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RENTECH AS own?

RENTECH AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RENTECH AS

Who owns RENTECH AS?

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

What is the revenue of RENTECH AS?

RENTECH AS had revenue of NOK 0 in 2025.

Who is the general manager of RENTECH AS?

Pål Renli is registered as general manager of RENTECH AS.

Where is RENTECH AS based?

RENTECH AS has its business address in Fornebu.

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.