BIZTRAC BETA
Joinery installation

VYVO BYGG AS

Org. no. 921373511 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 4.4m
Operating profit NOK −312,000
Equity NOK −138,000
Incorporated 2018
Employees 5
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−138k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−312k kr).

VYVO BYGG AS is registered as a limited company in Oslo, Oslo with organisation number 921373511. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2018 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Oppussingstjenester, maling, rehabilitering av baderom, legging av fliser og paneler.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.4m in revenue and NOK −312,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.4m
Operating profit
NOK −312,000
Equity
NOK −138,000

Financial health · 2024

Liquidity
0.78
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-13.3%
Weak
Equity as a share of total capital

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

Who owns VYVO BYGG AS?

DANIEL DROBIAZG
VYVO BYGG AS
NOK 4.4m rev. · NOK −312,000 profit

VYVO BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VYVO BYGG AS

Who owns VYVO BYGG AS?

DANIEL DROBIAZG is the largest registered owner, with 100.0%.

What is the revenue of VYVO BYGG AS?

VYVO BYGG AS had revenue of NOK 4.4m in 2024.

Who is the general manager of VYVO BYGG AS?

Daniel Drobiazg is registered as general manager of VYVO BYGG AS.

Where is VYVO BYGG AS based?

VYVO BYGG AS has its business address in Oslo.

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.