BIZTRAC BETA
Rental and operating of own or leased real estate

IDEBOLIG ARKITEKT OG BYGG AS

Org. no. 932241226 Limited company (AS) Hamar Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −8,000
Equity NOK 17,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

IDEBOLIG ARKITEKT OG BYGG AS is registered as a limited company in Hamar, Innlandet with organisation number 932241226. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Arkitekttjenester, byggesøknader, byggeteknisk prosjektering, prosjektledelse og utførelse av byggeprosjekter, Bygg og anlegg, Boligbygging, samt annen virksomhet som naturlig hører sammen med dette.”.

Key figures · 2024

Operating profit
NOK −8,000
Equity
NOK 17,000
Est. value
NOK 15,000

Financial health · 2024

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

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

Who owns IDEBOLIG ARKITEKT OG BYGG AS?

SANGAR KADER SALEH
IDEBOLIG ARKITEKT OG BYGG AS
· NOK −8,000 profit

IDEBOLIG ARKITEKT OG BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about IDEBOLIG ARKITEKT OG BYGG AS

Who owns IDEBOLIG ARKITEKT OG BYGG AS?

SANGAR KADER SALEH is the largest registered owner, with 100.0%.

Who is the general manager of IDEBOLIG ARKITEKT OG BYGG AS?

Sangar Kader Saleh is registered as general manager of IDEBOLIG ARKITEKT OG BYGG AS.

Where is IDEBOLIG ARKITEKT OG BYGG AS based?

IDEBOLIG ARKITEKT OG BYGG AS has its business address in Hamar.

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.