biztrac. BETA
COMPANY REGISTER PROFILE
994209833 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

OPULENS NÆRING 2 AS

Org. no. 994209833 Limited company (AS) Oslo Incorporated 2009 Active
Revenue 2025 NOK 16.7m
Operating profit NOK 8.0m
Equity NOK 204.3m
Incorporated 2009
Share capital NOK 40.0m

OPULENS NÆRING 2 AS is registered as a limited company in Oslo, Oslo with organisation number 994209833. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 40.0m, divided into 400000 shares. The company's stated purpose is: “Kjøpe, selge og eie næringseiendommer og deltakelse i selskaper innen næringsdrift.”. The most recent filed accounts, for the 2025 financial year, show NOK 16.7m in revenue and NOK 8.0m in operating profit.

Former names: BALDER NÆRING 2 AS

Key figures · 2025

Revenue
NOK 16.7m
▲ +24 %
Operating profit
NOK 8.0m
▲ +50 %
Equity
NOK 204.3m
▼ −0 %
Est. value
NOK 151.5m

Financial health · 2025

Liquidity
0.22
Not satisfactory
Current assets ÷ current liabilities
Profitability
5.6%
Weak
Return on total assets
Solidity
66.6%
Very good
Equity as a share of total capital

Who owns OPULENS NÆRING 2 AS?

OPULENS NÆRING 2 AS
NOK 16.7m rev. · NOK 8.0m profit

OPULENS NÆRING 2 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OPULENS NÆRING 2 AS

Who owns OPULENS NÆRING 2 AS?

OPULENS AS is the largest registered owner, with 100.0%.

What is the revenue of OPULENS NÆRING 2 AS?

OPULENS NÆRING 2 AS had revenue of NOK 16.7m in 2025.

Who is the general manager of OPULENS NÆRING 2 AS?

Trond Nilsen is registered as general manager of OPULENS NÆRING 2 AS.

Where is OPULENS NÆRING 2 AS based?

OPULENS NÆRING 2 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.