biztrac. BETA
COMPANY REGISTER PROFILE
921016085 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Retail sale of information and communication equipment

PROLYDAV AS

Org. no. 921016085 Limited company (AS) Tønsberg Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 3.1m
Operating profit NOK 728,000
Equity NOK 2.4m
Incorporated 2018
Share capital NOK 45,000

PROLYDAV AS is registered as a limited company in Tønsberg, Vestfold with organisation number 921016085. The business is classified under retail sale of information and communication equipment (NACE 47.400). The company was incorporated in 2018. Registered share capital is NOK 45,000, divided into 1500 shares. The company's stated purpose is: “Kjøp, salg og utleie av handelsvarer og kapitalvarer, i hovedsak brunevarer. Selskapet vil også kunne investere i fast eiendom, for salg eller utleie.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.1m in revenue and NOK 728,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.1m
▼ −18 %
Operating profit
NOK 728,000
▼ −11 %
Equity
NOK 2.4m
▲ +32 %
Est. value
NOK 3.8m

Financial health · 2025

Liquidity
2.41
Very good
Current assets ÷ current liabilities
Profitability
27.2%
Very good
Return on total assets
Solidity
81.3%
Very good
Equity as a share of total capital

Who owns PROLYDAV AS?

PROLYDAV AS
NOK 3.1m rev. · NOK 728,000 profit

PROLYDAV AS has 2 registered shareholders:

All shareholders and roles →

Which companies does PROLYDAV AS own?

PROLYDAV AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PROLYDAV AS

Who owns PROLYDAV AS?

KING INVEST AS is the largest registered owner, with 75.0%.

What is the revenue of PROLYDAV AS?

PROLYDAV AS had revenue of NOK 3.1m in 2025.

Where is PROLYDAV AS based?

PROLYDAV AS has its business address in Tønsberg.

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

Report a problem

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