BIZTRAC BETA
Development of building projects

VANGEN INVESTMENT AS

Org. no. 928658473 Limited company (AS) Færder Incorporated 1979 Active
Ownership graph ↗
Revenue 2024 NOK 267,000
Operating profit NOK 106,000
Equity NOK 1.4m
Incorporated 1979
Share capital NOK 102,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

VANGEN INVESTMENT AS is registered as a limited company in Færder, Vestfold with organisation number 928658473. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 1979. Registered share capital is NOK 102,000, divided into 1020 shares. The company's stated purpose is: “Eiendomsutvikling samt import og salg av varer.”. The most recent filed accounts, for the 2024 financial year, show NOK 267,000 in revenue and NOK 106,000 in operating profit.

Key figures · 2024

Revenue
NOK 267,000
Operating profit
NOK 106,000
Equity
NOK 1.4m
Est. value
NOK 1.1m

Financial health · 2024

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

Who owns VANGEN INVESTMENT AS?

MOR VANGEN AS
VANGEN INVESTMENT AS
NOK 267,000 rev. · NOK 106,000 profit

VANGEN INVESTMENT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VANGEN INVESTMENT AS

Who owns VANGEN INVESTMENT AS?

MOR VANGEN AS is the largest registered owner, with 100.0%.

What is the revenue of VANGEN INVESTMENT AS?

VANGEN INVESTMENT AS had revenue of NOK 267,000 in 2024.

Who is the general manager of VANGEN INVESTMENT AS?

Simon Edvardsen is registered as general manager of VANGEN INVESTMENT AS.

Where is VANGEN INVESTMENT AS based?

VANGEN INVESTMENT AS has its business address in Tjøme.

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.