BIZTRAC BETA
Development of building projects

VEGSTEIN J. A. EIENDOM AS

Org. no. 916683553 Limited company (AS) Vega Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 30,000
Operating profit NOK −18,000
Equity NOK 741,000
Incorporated 2016
Share capital NOK 100,000

Signals

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

VEGSTEIN J. A. EIENDOM AS is registered as a limited company in Vega, Nordland with organisation number 916683553. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2016. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utvikling og omsetning av eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 30,000 in revenue and NOK −18,000 in operating profit.

Key figures · 2024

Revenue
NOK 30,000
Operating profit
NOK −18,000
Equity
NOK 741,000
Est. value
NOK 547,000

Financial health · 2024

Liquidity
262.60
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
94.8%
Very good
Equity as a share of total capital

Who owns VEGSTEIN J. A. EIENDOM AS?

ANDRE MØLLER
VEGSTEIN J. A. EIENDOM AS
NOK 30,000 rev. · NOK −18,000 profit

VEGSTEIN J. A. EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VEGSTEIN J. A. EIENDOM AS

Who owns VEGSTEIN J. A. EIENDOM AS?

ANDRE MØLLER is the largest registered owner, with 50.0%.

What is the revenue of VEGSTEIN J. A. EIENDOM AS?

VEGSTEIN J. A. EIENDOM AS had revenue of NOK 30,000 in 2024.

Who is the general manager of VEGSTEIN J. A. EIENDOM AS?

Jarle Petter Ulriksen is registered as general manager of VEGSTEIN J. A. EIENDOM AS.

Where is VEGSTEIN J. A. EIENDOM AS based?

VEGSTEIN J. A. EIENDOM AS has its business address in Vega.

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.