BIZTRAC BETA
Business and other management consultancy activities

VYER AS

Org. no. 911962055 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 193,000
Operating profit NOK 88,000
Equity NOK 98,000
Incorporated 2013
Share capital NOK 30,000

VYER AS is registered as a limited company in Oslo, Oslo with organisation number 911962055. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å levere tjenester innen opplæring, rådgivning, redigering, og andre tjenester/produkter 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 foretagenger.”. The most recent filed accounts, for the 2025 financial year, show NOK 193,000 in revenue and NOK 88,000 in operating profit.

Key figures · 2025

Revenue
NOK 193,000
Operating profit
NOK 88,000
Equity
NOK 98,000
Est. value
NOK 333,000

Financial health · 2025

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

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

Who owns VYER AS?

LEIF ZERACH KNUTSEN
VYER AS
NOK 193,000 rev. · NOK 88,000 profit

VYER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VYER AS

Who owns VYER AS?

LEIF ZERACH KNUTSEN is the largest registered owner, with 100.0%.

What is the revenue of VYER AS?

VYER AS had revenue of NOK 193,000 in 2025.

Who is the general manager of VYER AS?

Leif Zerach Knutsen is registered as general manager of VYER AS.

Where is VYER AS based?

VYER AS has its business address in Oslo.

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.