biztrac. BETA
COMPANY REGISTER PROFILE
835653862 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

VITASBYGG AS

Org. no. 835653862 Limited company (AS) Enebakk Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 16.2m
Operating profit NOK 1.6m
Equity NOK 1.4m
Incorporated 2025
Employees 26
Share capital NOK 300,000

Signals

1 flags
  • Nylig endring 2026-06-17 Adresseendring registrert 2026-06-17.

VITASBYGG AS is registered as a limited company in Enebakk, Akershus with organisation number 835653862. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2025 and has 26 registered employees. Registered share capital is NOK 300,000, divided into 1000 shares. The company's stated purpose is: “Oppføring av bygninger, kjøp og salg av varer/tjenester innen bygg og anlegg, herunder import av varer fra utlandet.”. The most recent filed accounts, for the 2025 financial year, show NOK 16.2m in revenue and NOK 1.6m in operating profit.

Key figures · 2025

Revenue
NOK 16.2m
Operating profit
NOK 1.6m
Equity
NOK 1.4m
Est. value
NOK 4.7m

Financial health · 2025

Liquidity
1.24
Satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
18.9%
Good
Equity as a share of total capital

Who owns VITASBYGG AS?

VITASBYGG AS
NOK 16.2m rev. · NOK 1.6m profit

VITASBYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VITASBYGG AS

Who owns VITASBYGG AS?

DTT BYGG AS is the largest registered owner, with 70.0%.

What is the revenue of VITASBYGG AS?

VITASBYGG AS had revenue of NOK 16.2m in 2025.

Who is the general manager of VITASBYGG AS?

Vytautas Ulpys is registered as general manager of VITASBYGG AS.

Where is VITASBYGG AS based?

VITASBYGG AS has its business address in Ytre Enebakk.

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.