biztrac. BETA
COMPANY REGISTER PROFILE
936517528 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Installation of insulation

ESIT ISOLERING AS

Org. no. 936517528 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 153,000
Operating profit NOK −11,000
Equity NOK 7,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

ESIT ISOLERING AS is registered as a limited company in Oslo, Oslo with organisation number 936517528. The business is classified under installation of insulation (NACE 43.230). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Isolere rør med isolasjon.”. The most recent filed accounts, for the 2025 financial year, show NOK 153,000 in revenue and NOK −11,000 in operating profit.

Key figures · 2025

Revenue
NOK 153,000
Operating profit
NOK −11,000
Equity
NOK 7,000
Est. value
NOK 56,000

Financial health · 2025

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

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

Who owns ESIT ISOLERING AS?

ESIT ISOLERING AS
NOK 153,000 rev. · NOK −11,000 profit

ESIT ISOLERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ESIT ISOLERING AS

Who owns ESIT ISOLERING AS?

Ahmad Badrkhan is the largest registered owner, with 100.0%.

What is the revenue of ESIT ISOLERING AS?

ESIT ISOLERING AS had revenue of NOK 153,000 in 2025.

Who is the general manager of ESIT ISOLERING AS?

Ahmad Badrkhan is registered as general manager of ESIT ISOLERING AS.

Where is ESIT ISOLERING AS based?

ESIT ISOLERING 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.