biztrac. BETA
COMPANY REGISTER PROFILE
933792080 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other information technology and computer service activities

VATLAS AS

Org. no. 933792080 Limited company (AS) Kvinnherad Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −4,000
Equity NOK 13,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4k kr).
  • Nylig endring 2026-10-07 Avregistrert registrert 2026-10-07.

VATLAS AS is registered as a limited company in Kvinnherad, Vestland with organisation number 933792080. The business is classified under other information technology and computer service activities (NACE 62.900). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “3D-teknologi og VR.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −4,000
▲ +45 %
Equity
NOK 13,000
▼ −24 %

Financial health · 2025

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

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

Who owns VATLAS AS?

VATLAS AS
NOK 0 rev. · NOK −4,000 profit

VATLAS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VATLAS AS

Who owns VATLAS AS?

AME FORTIFY AS is the largest registered owner, with 100.0%.

What is the revenue of VATLAS AS?

VATLAS AS had revenue of NOK 0 in 2025.

Who is the general manager of VATLAS AS?

Espen Bauge is registered as general manager of VATLAS AS.

Where is VATLAS AS based?

VATLAS AS has its business address in Valen.

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.