BIZTRAC BETA
Veterinary activities

VEVIOS AS

Org. no. 927385007 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −12,000
Equity NOK −14,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−14k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−12k kr).

VEVIOS AS is registered as a limited company in Oslo, Oslo with organisation number 927385007. The business is classified under veterinary activities (NACE 75.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000000 shares. The company's stated purpose is: “Investering i aksjer, andeler, andre verdipapirer, fast eiendom, samt kjøp, salg, drift, utleie, tjenesteytelser og annen virksomhet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −12,000
Equity
NOK −14,000

Financial health · 2025

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

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

Who owns VEVIOS AS?

J.T. BIRKELAND HOLDING AS
VEVIOS AS
NOK 0 rev. · NOK −12,000 profit

VEVIOS AS has 2 registered shareholders:

All shareholders and roles →

Which companies does VEVIOS AS own?

VEVIOS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VEVIOS AS

Who owns VEVIOS AS?

J.T. BIRKELAND HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of VEVIOS AS?

VEVIOS AS had revenue of NOK 0 in 2025.

Where is VEVIOS AS based?

VEVIOS 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.