BIZTRAC BETA
Construction of residential and non-residential buildings

VEXO PROSJEKT AS

Org. no. 935361915 Limited company (AS) Nannestad Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 1.8m
Equity NOK 1.5m
Incorporated 2025
Share capital NOK 30,000

VEXO PROSJEKT AS is registered as a limited company in Nannestad, Akershus with organisation number 935361915. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen oppføring av bygninger og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 1.8m in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK 1.8m
Equity
NOK 1.5m
Est. value
NOK 6.0m

Financial health · 2025

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

Who owns VEXO PROSJEKT AS?

NIKOLAJ BRUN BJERREGAARD
VEXO PROSJEKT AS
NOK 1.9m rev. · NOK 1.8m profit

VEXO PROSJEKT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VEXO PROSJEKT AS

Who owns VEXO PROSJEKT AS?

NIKOLAJ BRUN BJERREGAARD is the largest registered owner, with 100.0%.

What is the revenue of VEXO PROSJEKT AS?

VEXO PROSJEKT AS had revenue of NOK 1.9m in 2025.

Who is the general manager of VEXO PROSJEKT AS?

Nikolaj Brun Bjerregaard is registered as general manager of VEXO PROSJEKT AS.

Where is VEXO PROSJEKT AS based?

VEXO PROSJEKT AS has its business address in Maura.

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.