BIZTRAC BETA
Work training and permanently adapted work

ASVO-VARDØ AS

Org. no. 965071377 Limited company (AS) Vardø Incorporated 1992 Active
Ownership graph ↗
Revenue 2024 NOK 7.3m
Operating profit NOK 525,000
Equity NOK 3.2m
Incorporated 1992
Employees 6
Share capital NOK 650,000

ASVO-VARDØ AS is registered as a limited company in Vardø, Finnmark with organisation number 965071377. The business is classified under work training and permanently adapted work (NACE 88.993). The company was incorporated in 1992 and has 6 registered employees. Registered share capital is NOK 650,000, divided into 50 shares. The company's stated purpose is: “Skape varige arbeidsplasser tilpasset de yrkes- hemmede som ikke uten videre kan nyttiggjøre seg andre arbeidstilbud. Grunnlaget for syssel- settingen skal baseres på framstilling av varer og tjenester for det ordinære marked. Sysselsettingen skal bidra til å kvalifisere og utvikle ressurser hos de yrkeshemmede.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.3m in revenue and NOK 525,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.3m
Operating profit
NOK 525,000
Equity
NOK 3.2m
Est. value
NOK 4.2m

Financial health · 2024

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

Who owns ASVO-VARDØ AS?

No shareholders are registered for ASVO-VARDØ AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about ASVO-VARDØ AS

What is the revenue of ASVO-VARDØ AS?

ASVO-VARDØ AS had revenue of NOK 7.3m in 2024.

Who is the general manager of ASVO-VARDØ AS?

Anita Brækkan Remme is registered as general manager of ASVO-VARDØ AS.

Where is ASVO-VARDØ AS based?

ASVO-VARDØ AS has its business address in Vardø.

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.