BIZTRAC BETA
Uoppgitt

MAJORVEGEN 16 AS

Org. no. 929141202 Limited company (AS) Nannestad Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −64,000
Equity NOK −97,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−97k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−64k kr).

MAJORVEGEN 16 AS is registered as a limited company in Nannestad, Akershus with organisation number 929141202. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investering i fast eiendom og andre selskaper. I tillegg hva styret finner interessant for selskapet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −64,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −64,000
Equity
NOK −97,000

Financial health · 2024

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

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

Who owns MAJORVEGEN 16 AS?

NOR-BO AS
MAJORVEGEN 16 AS
NOK 0 rev. · NOK −64,000 profit

MAJORVEGEN 16 AS has 2 registered shareholders:

All shareholders and roles →

Which companies does MAJORVEGEN 16 AS own?

MAJORVEGEN 16 AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MAJORVEGEN 16 AS

Who owns MAJORVEGEN 16 AS?

NOR-BO AS is the largest registered owner, with 66.7%.

What is the revenue of MAJORVEGEN 16 AS?

MAJORVEGEN 16 AS had revenue of NOK 0 in 2024.

Where is MAJORVEGEN 16 AS based?

MAJORVEGEN 16 AS has its business address in Nannestad.

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.