BIZTRAC BETA
Manufacture of other builders' carpentry and joinery

BOLIGVERKET AS

Org. no. 833751042 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Equity NOK 30,000
Incorporated 2024
Share capital NOK 30,000

BOLIGVERKET AS is registered as a limited company in Oslo, Oslo with organisation number 833751042. The business is classified under manufacture of other builders' carpentry and joinery (NACE 16.230). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selv, og/eller gjennom heleide eller deleide selskaper, drive salg, prosjektering og produksjon av nøkkelferdige mikrohus, modulhus, hus, bygninger, byggematerialer og interiør samt tilhørende entreprenørvirksomhet. Videre skal selskapet drive forvaltning og utleie av fast og løs eiendom, drive handel med verdipapirer samt utføre annen virksomhet som står i forbindelse med de nevnte aktiviteter. Selskapet skal også investere i eiendommer og virksomheter, drive teknologiutvikling i og utenfor EU med tilhørende virksomhet.”.

Key figures · 2024

Equity
NOK 30,000
Est. value
NOK 35,000

Financial health · 2024

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

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

Who owns BOLIGVERKET AS?

STERN GRUPPEN AB SELSKAP
BOLIGVERKET AS

BOLIGVERKET AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about BOLIGVERKET AS

Who owns BOLIGVERKET AS?

STERN GRUPPEN AB SELSKAP is the largest registered owner, with 74.0%.

Who is the general manager of BOLIGVERKET AS?

Ferhat Emre Yildiz is registered as general manager of BOLIGVERKET AS.

Where is BOLIGVERKET AS based?

BOLIGVERKET 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.