BIZTRAC BETA
Development of building projects

MOVIKVEIEN 16 AS

Org. no. 826625562 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −1,000
Equity NOK 26,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

MOVIKVEIEN 16 AS is registered as a limited company in Oslo, Oslo with organisation number 826625562. 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 300 shares. The company's stated purpose is: “Utvikling av tomt/eiendom for videresalg.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −1,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −1,000
Equity
NOK 26,000
Est. value
NOK 23,000

Financial health · 2024

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

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

Who owns MOVIKVEIEN 16 AS?

BM PROSJEKT OG UTVIKLING AS
MOVIKVEIEN 16 AS
NOK 0 rev. · NOK −1,000 profit

MOVIKVEIEN 16 AS has 3 registered shareholders:

All shareholders and roles →

Group structure

MOVIKVEIEN 16 AS er morselskap for 1 datterselskap:

Frequently asked questions about MOVIKVEIEN 16 AS

Who owns MOVIKVEIEN 16 AS?

BM PROSJEKT OG UTVIKLING AS is the largest registered owner, with 66.0%.

What is the revenue of MOVIKVEIEN 16 AS?

MOVIKVEIEN 16 AS had revenue of NOK 0 in 2024.

Who is the general manager of MOVIKVEIEN 16 AS?

Bujamin Ali is registered as general manager of MOVIKVEIEN 16 AS.

Where is MOVIKVEIEN 16 AS based?

MOVIKVEIEN 16 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.