BIZTRAC BETA
Rental and operating of own or leased real estate

FORENSIS HOLDING AS

Org. no. 914748550 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −1,000
Equity NOK 1.4m
Incorporated 2014
Share capital NOK 100,000

Signals

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

FORENSIS HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 914748550. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investeringer i aksjer, andre verdipapirer og fast eiendom samt hva som står i den forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −1,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −1,000
Equity
NOK 1.4m
Est. value
NOK 6.6m

Financial health · 2025

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

Who owns FORENSIS HOLDING AS?

SIDRA SAHAR BHATTI
FORENSIS HOLDING AS
NOK 0 rev. · NOK −1,000 profit

FORENSIS HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FORENSIS HOLDING AS own?

FORENSIS HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about FORENSIS HOLDING AS

Who owns FORENSIS HOLDING AS?

SIDRA SAHAR BHATTI is the largest registered owner, with 100.0%.

What is the revenue of FORENSIS HOLDING AS?

FORENSIS HOLDING AS had revenue of NOK 0 in 2025.

Where is FORENSIS HOLDING AS based?

FORENSIS HOLDING 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 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.