biztrac. BETA
COMPANY REGISTER PROFILE
836032152 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Joinery installation

YAZDAN BYGG ENTREPRENØR AS

Org. no. 836032152 Limited company (AS) Bærum Incorporated 2025 Active
Revenue 2025 NOK 763,000
Operating profit NOK 251,000
Equity NOK 216,000
Incorporated 2025
Share capital NOK 30,000

YAZDAN BYGG ENTREPRENØR AS is registered as a limited company in Bærum, Akershus with organisation number 836032152. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Snekker-og entreprenørtjenester, eiendomsutvikling og investeringer.”. The most recent filed accounts, for the 2025 financial year, show NOK 763,000 in revenue and NOK 251,000 in operating profit.

Key figures · 2025

Revenue
NOK 763,000
Operating profit
NOK 251,000
Equity
NOK 216,000
Est. value
NOK 832,000

Financial health · 2025

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

Who owns YAZDAN BYGG ENTREPRENØR AS?

YAZDAN BYGG ENTREPRENØR AS
NOK 763,000 rev. · NOK 251,000 profit

YAZDAN BYGG ENTREPRENØR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about YAZDAN BYGG ENTREPRENØR AS

Who owns YAZDAN BYGG ENTREPRENØR AS?

YAZDAN HOLDING AS is the largest registered owner, with 60.0%.

What is the revenue of YAZDAN BYGG ENTREPRENØR AS?

YAZDAN BYGG ENTREPRENØR AS had revenue of NOK 763,000 in 2025.

Who is the general manager of YAZDAN BYGG ENTREPRENØR AS?

Aram Yazdanparast is registered as general manager of YAZDAN BYGG ENTREPRENØR AS.

Where is YAZDAN BYGG ENTREPRENØR AS based?

YAZDAN BYGG ENTREPRENØR AS has its business address in Skui.

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.