BIZTRAC BETA
Research and experimental development on natural sciences and engineering

PLUVIA AS

Org. no. 916635559 Limited company (AS) Bergen Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK −8.7m
Equity NOK 3.9m
Incorporated 2015
Employees 5
Share capital NOK 171,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−8,7 mill kr).
  • Nylig endring 2026-04-14 Aksjekapital registrert 2026-04-14.

PLUVIA AS is registered as a limited company in Bergen, Vestland with organisation number 916635559. The business is classified under research and experimental development on natural sciences and engineering (NACE 72.100). The company was incorporated in 2015 and has 5 registered employees. Registered share capital is NOK 171,000, divided into 171374 shares. The company's stated purpose is: “Utvikle human medisin og det som hermed hører til.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK −8.7m in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK −8.7m
Equity
NOK 3.9m
Est. value
NOK 3.8m

Financial health · 2024

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

Who owns PLUVIA AS?

SARSIA SEED FOND II AS
PLUVIA AS
NOK 1.8m rev. · NOK −8.7m profit

PLUVIA AS has 11 registered shareholders:

All shareholders and roles →

Frequently asked questions about PLUVIA AS

Who owns PLUVIA AS?

SARSIA SEED FOND II AS is the largest registered owner, with 33.4%.

What is the revenue of PLUVIA AS?

PLUVIA AS had revenue of NOK 1.8m in 2024.

Who is the general manager of PLUVIA AS?

Torgeir Vaage is registered as general manager of PLUVIA AS.

Where is PLUVIA AS based?

PLUVIA AS has its business address in Bergen.

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.