BIZTRAC BETA
Other content distribution activities

VY IPR AS

Org. no. 932516489 Limited company (AS) Steinkjer Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 706,000
Operating profit NOK 598,000
Equity NOK 40,000
Incorporated 2023
Share capital NOK 30,000

VY IPR AS is registered as a limited company in Steinkjer, Trøndelag with organisation number 932516489. The business is classified under other content distribution activities (NACE 60.390). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2025 financial year, show NOK 706,000 in revenue and NOK 598,000 in operating profit.

Key figures · 2025

Revenue
NOK 706,000
Operating profit
NOK 598,000
Equity
NOK 40,000
Est. value
NOK 1.8m

Financial health · 2025

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

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

Who owns VY IPR AS?

JEVIG HOLDING AS
VY IPR AS
NOK 706,000 rev. · NOK 598,000 profit

VY IPR AS has 2 registered shareholders:

All shareholders and roles →

Which companies does VY IPR AS own?

VY IPR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VY IPR AS

Who owns VY IPR AS?

JEVIG HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of VY IPR AS?

VY IPR AS had revenue of NOK 706,000 in 2025.

Where is VY IPR AS based?

VY IPR AS has its business address in Steinkjer.

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.