BIZTRAC BETA
Wholesale of pharmaceutical and medical goods

UNO VITA AS

Org. no. 994731742 Limited company (AS) Moss Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 8.7m
Operating profit NOK 169,000
Equity NOK 2.6m
Incorporated 2009
Share capital NOK 1.6m

UNO VITA AS is registered as a limited company in Moss, Østfold with organisation number 994731742. The business is classified under wholesale of pharmaceutical and medical goods (NACE 46.460). The company was incorporated in 2009. Registered share capital is NOK 1.6m, divided into 1570000 shares. The company's stated purpose is: “Forskning, utvikling, behandling, kurs, kompetanseheving, rådgivning, informasjonsformidling, salg og distribusjon av medisinske produkter og metoder innen helsesektoren, drift av medisinsk klinikk og forskningsinstitusjon samt investeringer og deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.7m in revenue and NOK 169,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.7m
Operating profit
NOK 169,000
Equity
NOK 2.6m
Est. value
NOK 1.9m

Financial health · 2024

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

Who owns UNO VITA AS?

JAN FREDRIK POLESZYNSKI
UNO VITA AS
NOK 8.7m rev. · NOK 169,000 profit

UNO VITA AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about UNO VITA AS

Who owns UNO VITA AS?

JAN FREDRIK POLESZYNSKI is the largest registered owner, with 66.5%.

What is the revenue of UNO VITA AS?

UNO VITA AS had revenue of NOK 8.7m in 2024.

Who is the general manager of UNO VITA AS?

Jan Fredrik Poleszynski is registered as general manager of UNO VITA AS.

Where is UNO VITA AS based?

UNO VITA AS has its business address in Moss.

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.