BIZTRAC BETA
Other technical consultancy

AVI-LINK AS

Org. no. 968956868 Limited company (AS) Trondheim Incorporated 1994 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK −50,000
Equity NOK 437,000
Incorporated 1994
Share capital NOK 663,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−50k kr).

AVI-LINK AS is registered as a limited company in Trondheim, Trøndelag with organisation number 968956868. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 1994. Registered share capital is NOK 663,000, divided into 13250 shares. The company's stated purpose is: “Lett luftfart. Teknologivirksomhet vedrørende eller relatert til luftfartsteknologi, spesielt luftfartselektronikk samt aerodynamikk, strømningsdynamikk og energiomforming. Lett luftfart i sammenheng med teknologivirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK −50,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK −50,000
Equity
NOK 437,000
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns AVI-LINK AS?

GEIR MONSEN VAVIK
AVI-LINK AS
NOK 1.2m rev. · NOK −50,000 profit

AVI-LINK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about AVI-LINK AS

Who owns AVI-LINK AS?

GEIR MONSEN VAVIK is the largest registered owner, with 99.8%.

What is the revenue of AVI-LINK AS?

AVI-LINK AS had revenue of NOK 1.2m in 2025.

Who is the general manager of AVI-LINK AS?

Geir Monsen Vavik is registered as general manager of AVI-LINK AS.

Where is AVI-LINK AS based?

AVI-LINK AS has its business address in Jonsvatnet.

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.