BIZTRAC BETA
Development of building projects

BUSKERUDVEIEN BOLIG IV AS

Org. no. 927033380 Limited company (AS) Asker Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 6.1m
Operating profit NOK 1.2m
Equity NOK 30,000
Incorporated 2021
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.

BUSKERUDVEIEN BOLIG IV AS is registered as a limited company in Asker, Akershus with organisation number 927033380. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Kjøpe, eie, utvikle, oppføre og selge fast eiendom med dertil tilhørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.1m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 6.1m
Operating profit
NOK 1.2m
Equity
NOK 30,000
Est. value
NOK 3.2m

Financial health · 2024

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

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

Who owns BUSKERUDVEIEN BOLIG IV AS?

BUSKERUDVEIEN EIENDOM AS
BUSKERUDVEIEN BOLIG IV AS
NOK 6.1m rev. · NOK 1.2m profit

BUSKERUDVEIEN BOLIG IV AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BUSKERUDVEIEN BOLIG IV AS

Who owns BUSKERUDVEIEN BOLIG IV AS?

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

What is the revenue of BUSKERUDVEIEN BOLIG IV AS?

BUSKERUDVEIEN BOLIG IV AS had revenue of NOK 6.1m in 2024.

Where is BUSKERUDVEIEN BOLIG IV AS based?

BUSKERUDVEIEN BOLIG IV AS has its business address in Asker.

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.