BIZTRAC BETA
Buying and selling of own real estate

MAJORVEGEN 2 AS

Org. no. 923158006 Limited company (AS) Ullensaker Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK −74,000
Incorporated 2019
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−74k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MAJORVEGEN 2 AS is registered as a limited company in Ullensaker, Akershus with organisation number 923158006. The business is classified under buying and selling of own real estate (NACE 68.110). 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 og salg av eiendom, utleie av egen eller leid fast eiendom ellers, eiendomsutvikling og annet som står i forbindelse med dette, samt deltakelse i selskap med lignende formål.”.

Key figures · 2025

Operating profit
NOK −5,000
Equity
NOK −74,000

Financial health · 2025

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

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

Who owns MAJORVEGEN 2 AS?

FRYDENLUND HOLDING AS
MAJORVEGEN 2 AS
· NOK −5,000 profit

MAJORVEGEN 2 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MAJORVEGEN 2 AS

Who owns MAJORVEGEN 2 AS?

FRYDENLUND HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of MAJORVEGEN 2 AS?

Tor Vidar Frydenlund is registered as general manager of MAJORVEGEN 2 AS.

Where is MAJORVEGEN 2 AS based?

MAJORVEGEN 2 AS has its business address in Algarheim.

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.