biztrac. BETA
COMPANY REGISTER PROFILE
912683559 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

VAJA AS

Org. no. 912683559 Limited company (AS) Asker Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −21,000
Equity NOK −1.6m
Incorporated 2013
Share capital NOK 50,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,6 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−21k kr).

VAJA AS is registered as a limited company in Asker, Akershus with organisation number 912683559. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2013. Registered share capital is NOK 50,000, divided into 100 shares. The company's stated purpose is: “Eie og investere i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −21,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −21,000
▲ +80 %
Equity
NOK −1.6m
▲ +26 %

Financial health · 2025

Liquidity
0.24
Not satisfactory
Current assets ÷ current liabilities
Profitability
60.7%
Very good
Return on total assets
Solidity
-3118.7%
Weak
Equity as a share of total capital

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

Who owns VAJA AS?

VAJA AS
NOK 0 rev. · NOK −21,000 profit

VAJA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VAJA AS own?

VAJA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VAJA AS

Who owns VAJA AS?

Magnus Ørbeck-Nilssen is the largest registered owner, with 100.0%.

What is the revenue of VAJA AS?

VAJA AS had revenue of NOK 0 in 2025.

Where is VAJA AS based?

VAJA AS has its business address in Asker.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.