BIZTRAC BETA
Uoppgitt

SHIRIN JO AS

Org. no. 936536158 Limited company (AS) Lier Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −7,000
Equity NOK 24,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−6k kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-10-30.

SHIRIN JO AS is registered as a limited company in Lier, Buskerud with organisation number 936536158. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering av akskjer og deltagelser i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK 24,000
Est. value
NOK 28,000

Financial health · 2025

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

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

Who owns SHIRIN JO AS?

PEROOZ SARWARI
SHIRIN JO AS
NOK 0 rev. · NOK −7,000 profit

SHIRIN JO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SHIRIN JO AS own?

SHIRIN JO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SHIRIN JO AS

Who owns SHIRIN JO AS?

PEROOZ SARWARI is the largest registered owner, with 100.0%.

What is the revenue of SHIRIN JO AS?

SHIRIN JO AS had revenue of NOK 0 in 2025.

Who is the general manager of SHIRIN JO AS?

Perooz Sarwari is registered as general manager of SHIRIN JO AS.

Where is SHIRIN JO AS based?

SHIRIN JO AS has its business address in Tranby.

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.