BIZTRAC BETA
COMPANY REGISTER PROFILE
914753538 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Manufacture of pharmaceutical preparations

BELLEVACC AS

Org. no. 914753538 Limited company (AS) Ås Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −1.2m
Equity NOK 831,000
Incorporated 2014
Share capital NOK 175,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,2 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BELLEVACC AS is registered as a limited company in Ås, Akershus with organisation number 914753538. The business is classified under manufacture of pharmaceutical preparations (NACE 21.200). The company was incorporated in 2014. Registered share capital is NOK 175,000, divided into 175268 shares. The company's stated purpose is: “Utvikle og selge legemidler.”.

Key figures · 2025

Operating profit
NOK −1.2m
Equity
NOK 831,000
Est. value
NOK 976,000

Financial health · 2025

Liquidity
14.08
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
92.9%
Very good
Equity as a share of total capital

Who owns BELLEVACC AS?

BELLEVACC AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BELLEVACC AS

Who owns BELLEVACC AS?

PREVIWO AS is the largest registered owner, with 75.9%.

Where is BELLEVACC AS based?

BELLEVACC AS has its business address in Ås.

Property

Business address Høgskoleveien 8, 1433 Ås
Cadastral unit 3218-42/1/78/0

2 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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