BIZTRAC BETA
Development of building projects

VERKSTOPPEN BOLIGUTVIKLING AS

Org. no. 823792042 Limited company (AS) Fredrikstad Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 44.3m
Operating profit NOK 1.4m
Equity NOK 5.8m
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

VERKSTOPPEN BOLIGUTVIKLING AS is registered as a limited company in Fredrikstad, Østfold with organisation number 823792042. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp, utvikling, forvaltning og salg av faste eiendommer, samt delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 44.3m in revenue and NOK 1.4m in operating profit.

Key figures · 2025

Revenue
NOK 44.3m
Operating profit
NOK 1.4m
Equity
NOK 5.8m
Est. value
NOK 7.4m

Financial health · 2025

Liquidity
1.27
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
18.6%
Good
Equity as a share of total capital

Who owns VERKSTOPPEN BOLIGUTVIKLING AS?

SOLID EIENDOM AS
VERKSTOPPEN BOLIGUTVIKLING AS
NOK 44.3m rev. · NOK 1.4m profit

VERKSTOPPEN BOLIGUTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VERKSTOPPEN BOLIGUTVIKLING AS

Who owns VERKSTOPPEN BOLIGUTVIKLING AS?

SOLID EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of VERKSTOPPEN BOLIGUTVIKLING AS?

VERKSTOPPEN BOLIGUTVIKLING AS had revenue of NOK 44.3m in 2025.

Where is VERKSTOPPEN BOLIGUTVIKLING AS based?

VERKSTOPPEN BOLIGUTVIKLING AS has its business address in Rolvsøy.

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.